Re: [PATCH v2 2/2] kallsyms: Document why unresolved symbols are revealed

[Steven Rostedt]

On Mon, 31 Aug 2026 15:37:29 +0200
Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> wrote:

> Could someone yell here, please? I convinced myself that hiding
> unresolved pointers is the good thing to do here since a "wrong" pointer
> would be seen in backtrace anyway.
> 
> Thread starts at
> 	https://lore.kernel.org/all/20260821152614.2202196-1-bigeasy@xxxxxxxxxxxxx/

I wonder if we should just tagged hash values as such:

| [    1.498171]  <TASK>
| [    1.498172]  00000000cb9bc262 [hash]
| [    1.498174]  ? 00000000eb5021dd [hash]
| [    1.498176]  00000000ed1a9938 [hash]
| [    1.498178]  </TASK>

So that people will know that the value is just some random hash value and
not a real address.

Although rather useless in call stacks, I like hash values because the same
address will show up the same.

Having '[unknown]' may also be confusing because it doesn't really say
"why" it was unknown. But having a number goes back to what it always did.
Hashing it with a "[hash]" marker will also let people know the value was
hashed.

-- Steve