[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z86qacj2hchPyFGK@smile.fi.intel.com>
Date: Mon, 10 Mar 2025 11:01:29 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: David Laight <david.laight.linux@...il.com>
Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Christophe Leroy <christophe.leroy@....fr>,
Rasmus Villemoes <linux@...musvillemoes.dk>, nnac123@...ux.ibm.com,
horms@...nel.org
Subject: Re: [PATCH next 4/8] test_hexdump: Check for buffer overrun of
sample output buffer
On Sat, Mar 08, 2025 at 09:34:48AM +0000, David Laight wrote:
> While the output generated by test_hexdump_prepare_test() shouldn't
> be longer than the size of the buffer passed, for safety verify that
> the buffer is long enough.
> If too short fill the buffer with an error message - output on
> test failure.
Isn't the function should behave snprintf() alike?
I think this patch is simply wrong because it's based on a wrong assumption.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists