diff options
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | 2014-11-19 00:13:25 (GMT) |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2014-11-19 20:24:31 (GMT) |
commit | 9960efeb80f73bd073483dab0855ee0ddc27085c (patch) | |
tree | 2eb8c3ea46a6fe5636507c2411e59b0ed8716ae2 /kernel/trace/ftrace.c | |
parent | a9ce7c36aa4256019180c590d60e2fad7431c749 (diff) | |
download | linux-9960efeb80f73bd073483dab0855ee0ddc27085c.tar.xz |
ftrace/x86: Add frames pointers to trampoline as necessary
When CONFIG_FRAME_POINTERS are enabled, it is required that the
ftrace_caller and ftrace_regs_caller trampolines set up frame pointers
otherwise a stack trace from a function call wont print the functions
that called the trampoline. This is due to a check in
__save_stack_address():
#ifdef CONFIG_FRAME_POINTER
if (!reliable)
return;
#endif
The "reliable" variable is only set if the function address is equal to
contents of the address before the address the frame pointer register
points to. If the frame pointer is not set up for the ftrace caller
then this will fail the reliable test. It will miss the function that
called the trampoline. Worse yet, if fentry is used (gcc 4.6 and
beyond), it will also miss the parent, as the fentry is called before
the stack frame is set up. That means the bp frame pointer points
to the stack of just before the parent function was called.
Link: http://lkml.kernel.org/r/20141119034829.355440340@goodmis.org
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Cc: stable@vger.kernel.org # 3.7+
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/ftrace.c')
0 files changed, 0 insertions, 0 deletions