From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Justin He <Justin.He@arm.com>, Petr Mladek <pmladek@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Eric Biggers <ebiggers@google.com>,
"Ahmed S. Darwish" <a.darwish@linutronix.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH RFCv3 3/3] lib/test_printf: add test cases for '%pD'
Date: Tue, 15 Jun 2021 09:47:32 +0200 [thread overview]
Message-ID: <55513987-4ec5-be80-a458-28f275cb4f72@rasmusvillemoes.dk> (raw)
In-Reply-To: <AM6PR08MB4376096643BA02A1AE2BA8F4F7309@AM6PR08MB4376.eurprd08.prod.outlook.com>
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
next prev parent reply other threads:[~2021-06-15 7:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 15:59 [PATCH RFCv3 0/3] make '%pD' print full path for file Jia He
2021-06-11 15:59 ` [PATCH RFCv3 1/3] fs: introduce helper d_path_unsafe() Jia He
2021-06-11 15:59 ` [PATCH RFCv3 2/3] lib/vsprintf.c: make %pD print full path for file Jia He
2021-06-11 21:28 ` Rasmus Villemoes
2021-06-15 6:43 ` Justin He
2021-06-15 7:04 ` Rasmus Villemoes
2021-06-15 8:32 ` Justin He
2021-06-14 15:40 ` Petr Mladek
2021-06-15 6:48 ` Justin He
2021-06-15 7:14 ` Rasmus Villemoes
2021-06-15 7:18 ` Justin He
2021-06-15 14:48 ` Justin He
2021-06-11 15:59 ` [PATCH RFCv3 3/3] lib/test_printf: add test cases for '%pD' Jia He
2021-06-11 21:40 ` Rasmus Villemoes
2021-06-15 7:06 ` Justin He
2021-06-15 7:15 ` Justin He
2021-06-15 7:40 ` Rasmus Villemoes
2021-06-14 15:44 ` Petr Mladek
2021-06-15 7:07 ` Justin He
2021-06-15 7:47 ` Rasmus Villemoes [this message]
2021-06-15 7:56 ` Justin He
2021-06-15 8:19 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55513987-4ec5-be80-a458-28f275cb4f72@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=Justin.He@arm.com \
--cc=a.darwish@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=ebiggers@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).