[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db57e59c-5b15-9428-5daa-5dfa4a1d2be9@kernel.org>
Date: Tue, 19 Jan 2021 15:25:34 -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 3:15 PM, Steven Rostedt wrote:
> When it's not related to any symbol, doesn't it still produce an offset
> with something close by, that could still give you information that's
> better than a hashed number.
No. I often need the actual unhashed address in the hex dump so that I
can see if some other pointer is correct.
For example, I could be doing pointer math to calculate the address of
some data inside a block. In this case, I would %px the pointer, and
then hex_dump the block. I can then see not only where inside the block
the pointer is pointing to, but what data it points to.
Powered by blists - more mailing lists