[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210126123912.23a5c3a1@gandalf.local.home>
Date: Tue, 26 Jan 2021 12:39:12 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: 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, John Ogness <john.ogness@...utronix.de>,
linux-mm@...ck.org, Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [PATCH 0/2] introduce DUMP_PREFIX_UNHASHED for hex dumps
On Tue, 26 Jan 2021 11:30:02 -0600
Timur Tabi <timur@...nel.org> wrote:
> On 1/26/21 11:14 AM, Vlastimil Babka wrote:
> > If it was a boot option, I would personally be for leaving hashing enabled by
> > default, with opt-in boot option to disable it.
>
> A boot option would solve all my problems. I wouldn't need to recompile
> the kernel, and it would apply to all variations of printk.
Should it be called "make-printk-insecure"
?
-- Steve
Powered by blists - more mailing lists