[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a233bef-8ba6-82bb-9075-35793a244a3b@kernel.org>
Date: Thu, 11 Feb 2021 12:16:55 -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>,
Vlastimil Babka <vbabka@...e.cz>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Matthew Wilcox <willy@...radead.org>,
akpm@...ux-foundation.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
roman.fietze@...na.com, Kees Cook <keescook@...omium.org>,
John Ogness <john.ogness@...utronix.de>,
akinobu.mita@...il.com, glider@...gle.com,
Andrey Konovalov <andreyknvl@...gle.com>,
Marco Elver <elver@...gle.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Pavel Machek <pavel@....cz>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 3/3] [v3] lib/vsprintf: debug_never_hash_pointers prints
all addresses as unhashed
On 2/11/21 11:53 AM, Petr Mladek wrote:
> I would really like to make it clear here that it is not only about
> consoles. Most people will see only this message. Only few people read
> documentation. Many people will learn the parameter name from another
> context by googling.
>
> I know that it is not easy to find good words. Especially because
> pointers printed by %pK might still be hashed.
>
>> + pr_warn("** **\n");
>> + pr_warn("** Kernel memory addresses are exposed, which may **\n");
>> + pr_warn("** reduce the security of your system. **\n");
> What about replacing the first two paragraphs with something like:
>
> "This system shows unhashed kernel memory addresses via logs and
> other interfaces. It might reduce the security of your system."
That works, thanks. I'll post a v4 soon.
Powered by blists - more mailing lists