summaryrefslogtreecommitdiffstats
path: root/kernel/trace/tracing_map.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-08-17 16:37:25 -0400
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-08-24 10:04:01 -0400
commita8f0f9e49956a74718874b800251455680085600 (patch)
treed01ffa943d7a2382bdd50255a4949fa696737b66 /kernel/trace/tracing_map.c
parenta7e52ad7ed82e21273eccff93d1477a7b313aabb (diff)
downloadtalos-op-linux-a8f0f9e49956a74718874b800251455680085600.tar.gz
talos-op-linux-a8f0f9e49956a74718874b800251455680085600.zip
ftrace: Check for null ret_stack on profile function graph entry function
There's a small race when function graph shutsdown and the calling of the registered function graph entry callback. The callback must not reference the task's ret_stack without first checking that it is not NULL. Note, when a ret_stack is allocated for a task, it stays allocated until the task exits. The problem here, is that function_graph is shutdown, and a new task was created, which doesn't have its ret_stack allocated. But since some of the functions are still being traced, the callbacks can still be called. The normal function_graph code handles this, but starting with commit 8861dd303c ("ftrace: Access ret_stack->subtime only in the function profiler") the profiler code references the ret_stack on function entry, but doesn't check if it is NULL first. Link: https://bugzilla.kernel.org/show_bug.cgi?id=196611 Cc: stable@vger.kernel.org Fixes: 8861dd303c ("ftrace: Access ret_stack->subtime only in the function profiler") Reported-by: lilydjwg@gmail.com Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/tracing_map.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud