diff options
| author | Masami Hiramatsu <mhiramat@kernel.org> | 2021-10-21 09:55:17 +0900 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2021-10-22 12:16:53 -0400 |
| commit | b3ea5d56f212ad81328c82454829a736197ebccc (patch) | |
| tree | a54d87b8528abb2b6129f8c3239eef2515fd76e6 /arch/arm | |
| parent | cd9bc2c9258816dc934b300705076519d7375b81 (diff) | |
| download | linux-b3ea5d56f212ad81328c82454829a736197ebccc.tar.gz linux-b3ea5d56f212ad81328c82454829a736197ebccc.tar.bz2 linux-b3ea5d56f212ad81328c82454829a736197ebccc.zip | |
ARM: clang: Do not rely on lr register for stacktrace
Currently the stacktrace on clang compiled arm kernel uses the 'lr'
register to find the first frame address from pt_regs. However, that
is wrong after calling another function, because the 'lr' register
is used by 'bl' instruction and never be recovered.
As same as gcc arm kernel, directly use the frame pointer (r11) of
the pt_regs to find the first frame address.
Note that this fixes kretprobe stacktrace issue only with
CONFIG_UNWINDER_FRAME_POINTER=y. For the CONFIG_UNWINDER_ARM,
we need another fix.
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'arch/arm')
| -rw-r--r-- | arch/arm/kernel/stacktrace.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/arm/kernel/stacktrace.c b/arch/arm/kernel/stacktrace.c index 76ea4178a55c..db798eac7431 100644 --- a/arch/arm/kernel/stacktrace.c +++ b/arch/arm/kernel/stacktrace.c @@ -54,8 +54,7 @@ int notrace unwind_frame(struct stackframe *frame) frame->sp = frame->fp; frame->fp = *(unsigned long *)(fp); - frame->pc = frame->lr; - frame->lr = *(unsigned long *)(fp + 4); + frame->pc = *(unsigned long *)(fp + 4); #else /* check current frame pointer is within bounds */ if (fp < low + 12 || fp > high - 4) |