[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2de3a189-adca-4954-e2a3-c79fbe3eee96@kernel.org>
Date: Tue, 9 Feb 2021 16:15:20 -0600
From: Timur Tabi <timur@...nel.org>
To: Marco Elver <elver@...gle.com>
Cc: Petr Mladek <pmladek@...e.com>,
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,
akinobu.mita@...il.com, glider@...gle.com, andreyknvl@...gle.com
Subject: Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all
addresses as unhashed
On 2/9/21 3:59 PM, Marco Elver wrote:
> Would it be reasonable to make this non-static? Or somehow make it
> possible to get this flag from other subsystems?
>
> There are other places in the kernel that dump sensitive data such as
> registers. We'd like to be able to use 'debug_never_hash_pointers' to
> decide if our debugging tools can dump registers etc. What we really
> need is info if the kernel is in debug mode and we can dump all kinds of
> sensitive info; debug_never_hash_pointers is would be a good enough
> proxy for that.
The next version of my patch (coming soon) will export the symbol. It's
intended for test_printf, but if you think it can be used by others, so
much the better.
Powered by blists - more mailing lists