mirror of
https://github.com/torvalds/linux.git
synced 2026-06-08 22:52:35 +02:00
function-graph: Init curr_ret_stack with ret_stack
commit ea14eb7140 upstream.
If the graph tracer is active, and a task is forked but the allocating of
the processes graph stack fails, it can cause crash later on.
This is due to the temporary stack being NULL, but the curr_ret_stack
variable is copied from the parent. If it is not -1, then in
ftrace_graph_probe_sched_switch() the following:
for (index = next->curr_ret_stack; index >= 0; index--)
next->ret_stack[index].calltime += timestamp;
Will cause a kernel OOPS.
Found with Li Zefan's ftrace_stress_test.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
parent
9dfa691cae
commit
090fe6cbe1
|
|
@ -3258,6 +3258,7 @@ void ftrace_graph_init_task(struct task_struct *t)
|
|||
{
|
||||
/* Make sure we do not use the parent ret_stack */
|
||||
t->ret_stack = NULL;
|
||||
t->curr_ret_stack = -1;
|
||||
|
||||
if (ftrace_graph_active) {
|
||||
struct ftrace_ret_stack *ret_stack;
|
||||
|
|
@ -3267,7 +3268,6 @@ void ftrace_graph_init_task(struct task_struct *t)
|
|||
GFP_KERNEL);
|
||||
if (!ret_stack)
|
||||
return;
|
||||
t->curr_ret_stack = -1;
|
||||
atomic_set(&t->tracing_graph_pause, 0);
|
||||
atomic_set(&t->trace_overrun, 0);
|
||||
t->ftrace_timestamp = 0;
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user