Messages in this thread Patch in this message | | | From | Kent Overstreet <> | Subject | [PATCH 11/32] test_printf: Drop requirement that sprintf not write past nul | Date | Sun, 14 Aug 2022 17:19:50 -0400 |
| |
From: Kent Overstreet <kent.overstreet@gmail.com>
The current test code checks that sprintf never writes past the terminating nul. This is a rather strange requirement, completely separate from writing past the end of the buffer, which of course we can't do: writing anywhere to the buffer passed to snprintf, within size of course, should be perfectly fine.
Since this check has no documentation as to where it comes from or what depends on it, and it's getting in the way of further refactoring (printf_spec handling is right now scattered massively throughout the code, and we'd like to consolidate it) - delete it.
Also, many current pretty-printers building up their output on the stack, and then copy it to the actual output buffer - by eliminating this requirement we can kill those extra buffers.
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com> Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk> --- lib/test_printf.c | 6 ------ 1 file changed, 6 deletions(-)
diff --git a/lib/test_printf.c b/lib/test_printf.c index 4bd15a593f..da91301eae 100644 --- a/lib/test_printf.c +++ b/lib/test_printf.c @@ -84,12 +84,6 @@ do_test(int bufsize, const char *expect, int elen, return 1; } - if (memchr_inv(test_buffer + written + 1, FILL_CHAR, bufsize - (written + 1))) { - pr_warn("vsnprintf(buf, %d, \"%s\", ...) wrote beyond the nul-terminator\n", - bufsize, fmt); - return 1; - } - if (memchr_inv(test_buffer + bufsize, FILL_CHAR, BUF_SIZE + PAD_SIZE - bufsize)) { pr_warn("vsnprintf(buf, %d, \"%s\", ...) wrote beyond buffer\n", bufsize, fmt); return 1; -- 2.36.1
| |