[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mtwv8ptz.fsf@jogness.linutronix.de>
Date: Tue, 26 Jan 2021 20:29:36 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Steven Rostedt <rostedt@...dmis.org>, Timur Tabi <timur@...nel.org>
Cc: Vlastimil Babka <vbabka@...e.cz>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
Petr Mladek <pmladek@...e.com>, roman.fietze@...na.com,
keescook@...omium.org, linux-mm@...ck.org,
Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps
On 2021-01-26, Steven Rostedt <rostedt@...dmis.org> wrote:
> And even if we make this a boot time option, perhaps we should still
> include that nasty dmesg notice, which will let people know that the
> kernel has unhashed values.
+1
The notice would probably be the main motivation for distros/users to
avoid unhashed values unless truly debugging. Which is what we want.
John Ogness
Powered by blists - more mailing lists