[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19c1c17e-d0b3-326e-97ec-a4ec1ebee749@kernel.org>
Date: Wed, 3 Feb 2021 12:58:41 -0600
From: Timur Tabi <timur@...nel.org>
To: Petr Mladek <pmladek@...e.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
linux-kernel@...r.kernel.org, vbabka@...e.cz, linux-mm@...ck.org,
willy@...radead.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, roman.fietze@...na.com,
keescook@...omium.org, john.ogness@...utronix.de,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
akinobu.mita@...il.com
Subject: Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all
addresses as unhashed
On 2/3/21 7:31 AM, Petr Mladek wrote:
> Also please make sure that lib/test_printf.c will work with
> the new option.
As you suspected, it doesn't work:
[ 206.966478] test_printf: loaded.
[ 206.966528] test_printf: plain 'p' does not appear to be hashed
[ 206.966740] test_printf: failed 1 out of 388 tests
What should I do about this?
On one hand, it is working as expected: %p is not hashed, and that
should be a warning.
On the other hand, maybe test_printf should be aware of the command line
parameter and test to make sure that %p is NOT hashed?
Powered by blists - more mailing lists