Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
riscv: stacktrace: fix the riscv stacktrace when CONFIG_FRAME_POINTER…
… enabled As [1] and [2] said, the arch_stack_walk should not to trace itself, or it will leave the trace unexpectedly when called. The example is when we do "cat /sys/kernel/debug/page_owner", all pages' stack is the same. arch_stack_walk+0x18/0x20 stack_trace_save+0x40/0x60 register_dummy_stack+0x24/0x5e init_page_owner+0x2e So we use __builtin_frame_address(1) as the first frame to be walked. And mark the arch_stack_walk() noinline. We found that pr_cont will affact pages' stack whose task state is RUNNING when testing "echo t > /proc/sysrq-trigger". So move the place of pr_cont and mark the function dump_backtrace() noinline. Also we move the case when task == NULL into else branch, and test for it in "echo c > /proc/sysrq-trigger". [1] https://lore.kernel.org/lkml/[email protected]/ [2] https://lore.kernel.org/lkml/[email protected]/ Signed-off-by: Chen Huang <[email protected]> Fixes: 5d8544e ("RISC-V: Generic library routines and assembly") Cc: [email protected] Signed-off-by: Palmer Dabbelt <[email protected]>
- Loading branch information