Re: [RFC] kallsyms: embed source file:line info in kernel stack traces

Alexey Dobriyan
2026-03-03T19:08:09Z

On Tue, Mar 03, 2026 at 08:17:48AM -0500, Steven Rostedt wrote:
> On Tue, 3 Mar 2026 08:39:36 +0300
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > On Mon, Mar 02, 2026 at 03:28:28PM -0500, Sasha Levin wrote:
> > > [ 11.206749] dump_stack_lvl+0x5d/0x80 (lib/dump_stack.c:94)
> >
> > This is super useful, thanks.
> >
> > Can the 0x prefix be dropped as well?
>
> And print in decimal? Without the 0x, it could be ambiguous that it's hex.

Yes. It is ambigious only if someone doesn't know that previous kernels
always had 0x in the backtraces.

> I can see this being very useful when debugging something that causes a
> crash, as it will save me time from cat'ing the output into
> decode_stacktrace.pl after each crash. Although, I can see this having the
> same issue as gdb has with static inlined functions.

It is also useful for _not_ dealing with corporate rpm dumps.

Kernel started to print pagefault in string form at some point,
maybe it is time to finish the job with this patch and even go as far as
disassembly.

alexey+0/1