tracing: Have stack tracer trace full stack
The stack tracer traces every function call checking the current stack (in non interrupt context), looking for the deepest stack, and saving it when it finds a new max depth. The problem is that it calls save_stack_trace(), and with the new ORC unwinder, it can skip too much. As it looks at the ip of the function call in the backtrace to find where it should start, it doesn't need to skip anything. The stack trace selftest would fail when the kernel was complied with the ORC UNDWINDER enabled. Without skipping functions when doing the stack trace, it now passes again. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
This commit is contained in:
parent
da387e5c93
commit
a2acce5369
|
@ -111,7 +111,7 @@ check_stack(unsigned long ip, unsigned long *stack)
|
|||
stack_trace_max_size = this_size;
|
||||
|
||||
stack_trace_max.nr_entries = 0;
|
||||
stack_trace_max.skip = 3;
|
||||
stack_trace_max.skip = 0;
|
||||
|
||||
save_stack_trace(&stack_trace_max);
|
||||
|
||||
|
|
Loading…
Reference in New Issue