[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <184ab5eb-2508-0761-36c6-061d509fe104@kernel.org>
Date: Tue, 19 Jan 2021 14:49:17 -0600
From: Timur Tabi <timur@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Kees Cook <keescook@...omium.org>,
Matthew Wilcox <willy@...radead.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
Petr Mladek <pmladek@...e.com>, roman.fietze@...na.com,
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 1/19/21 2:10 PM, Steven Rostedt wrote:
> I'm curious, what is the result if you replaced %p with %pS?
>
> That way you get a kallsyms offset version of the output, which could still
> be very useful depending on what you are dumping.
%pS versatile_init+0x0/0x110
The address is question is often not related to any symbol, so it
wouldn't make sense to use %pS.
Maybe you meant %pK? I'm okay with that instead of %px.
Powered by blists - more mailing lists