Re: [PATCH V11 0/5] hash addresses printed with %p

From
Sergey Senozhatsky <hidden>
Date
2017-12-01 06:15:34
Also in
lkml
Reply to
Sergey Senozhatsky, 2017-11-30
On (11/30/17 19:26), Sergey Senozhatsky wrote:
On (11/30/17 10:23), David Laight wrote:
[..]
quoted
quoted
Maybe I'm being thick, but...  if we're rendering these addresses
unusable by hashing them, why not just print something like
"<obscured>" in their place?  That loses the uniqueness thing but I
wonder how valuable that is in practice?
My worry is that is you get a kernel 'oops' print with actual register
values you have no easy way of tying an address or address+offset to
the corresponding hash(address) printed elsewhere.
print the existing hash:pointer mappings in panic()? [if we can do that]
by this I meant
	"when oops_in_progress == 1 then print hash:pointer for %p,
	 not just hash".

	-ss
Thread (48 messages) 48 messages, 12 authors, last reply 2017-12-07
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help