diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2021-05-16 16:59:56 -0400 | 
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2022-08-21 11:50:42 -0400 | 
| commit | 89868773fe862eabc049aaa6f6b587177b3f2ea6 (patch) | |
| tree | 19ea9a9722389bdc3c7b297c9c3b3f84d3667d46 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 568035b01cfb107af8d2e4bd2fb9aea22cf5b868 (diff) | |
tomoyo: use vsnprintf() properly
Idiomatic way to find how much space sprintf output would take is
	len = snprintf(NULL, 0, ...) + 1;
Once upon a time there'd been libc implementations that blew chunks
on that and somebody had come up with the following "cute" trick:
	len = snprintf((char *) &len, 1, ...) + 1;
for doing the same.  However, that's unidiomatic, harder to follow
*and* any such libc implementation would violate both C99 and POSIX
(since 2001).
	IOW, this kludge is best buried along with such libc implementations,
nevermind getting cargo-culted into newer code.  Our vsnprintf() does not
suffer that braindamage, TYVM.
Acked-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions
