Skip to content

changes about Call Trace:

Akinobu Mita lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 17 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3makes print_symbol() return intinclude/linux/kallsyms.h kernel/kallsyms.c+12 -93 replies
2/3use usual call trace format on x86-64arch/x86_64/kernel/traps.c+7 -223 replies
3/3omit symbol size field in print_symbol()kernel/kallsyms.c+2 -34 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] changes about Call Trace:

Hello,

I realized two things when I was porting my small script oops2line to x86-64. (read call trace, find correspondance modules, calculate addr and addr2line)

If I'm missing something, please let me know.

a) On x86-64 we get different Call Trace format than other architectures when we get oops or press SysRq-t:

<ffffffffa008ef6c>{:jbd:kjournald+1030}

There is a architecture independent function print_symbol(). How about using it on x86-64? But it changes to:

[<ffffffffa008ef6c>] kjournald+0x406/0x578 [jbd]

b) I can't find useful usage for the symbol size in print_symbol(). And symbolsize seems to be fixed when vmlinux or modules are compiled. So we can calculate it from vmlinux or modules.
How about removing the field of symbolsize in print_symbol()?

[<ffffffffa008ef6c>] kjournald+0x406 [jbd]