[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55513987-4ec5-be80-a458-28f275cb4f72@rasmusvillemoes.dk>
Date: Tue, 15 Jun 2021 09:47:32 +0200
From: Rasmus Villemoes <linux@...musvillemoes.dk>
To: Justin He <Justin.He@....com>, Petr Mladek <pmladek@...e.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Jonathan Corbet <corbet@....net>,
Alexander Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Eric Biggers <ebiggers@...gle.com>,
"Ahmed S. Darwish" <a.darwish@...utronix.de>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH RFCv3 3/3] lib/test_printf: add test cases for '%pD'
On 15/06/2021 09.07, Justin He wrote:
> Hi Petr
>
>>> +static void __init
>>> +f_d_path(void)
>>> +{
>>> + test("(null)", "%pD", NULL);
>>> + test("(efault)", "%pD", PTR_INVALID);
>>> +
>>> + is_prepend_buf = true;
>>> + test("/bravo/alfa |/bravo/alfa ", "%-14pD|%*pD", &test_file, -14,
>> &test_file);
>>> + test(" /bravo/alfa| /bravo/alfa", "%14pD|%*pD", &test_file, 14,
>> &test_file);
>>> + test(" /bravo/alfa|/bravo/alfa ", "%14pD|%-14pD", &test_file,
>> &test_file);
>>
>> Please, add more test for scenarios when the path does not fit into
>> the buffer or when there are no limitations, ...
>
> Indeed, thanks
Doesn't the existing test() helper do this for you automatically?
/*
* Every fmt+args is subjected to four tests: Three where we
* tell vsnprintf varying buffer sizes (plenty, not quite
* enough and 0), and then we also test that kvasprintf would
* be able to print it as expected.
*/
I don't see why one would need to do anything special for %pD.
Rasmus
Powered by blists - more mailing lists