diff options
author | Mark Rutland <mark.rutland@arm.com> | 2023-04-11 17:29:41 +0100 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2023-04-11 18:34:59 +0100 |
commit | 9e09d445f1cab518eedf4454d119ead27979b8f4 (patch) | |
tree | e48a5ada92073bdab4e6d2003f673c16756fdacf /scripts/gdb/linux/vmalloc.py | |
parent | e8d018dd0257f744ca50a729e3d042cf2ec9da65 (diff) |
arm64: stacktrace: recover return address for first entry
The function which calls the top-level backtracing function may have
been instrumented with ftrace and/or kprobes, and hence the first return
address may have been rewritten.
Factor out the existing fgraph / kretprobes address recovery, and use
this for the first address. As the comment for the fgraph case isn't all
that helpful, I've also dropped that.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Kalesh Singh <kaleshsingh@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Madhavan T. Venkataraman <madvenka@linux.microsoft.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>
Link: https://lore.kernel.org/r/20230411162943.203199-2-mark.rutland@arm.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/vmalloc.py')
0 files changed, 0 insertions, 0 deletions