diff options
| author | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-08-09 21:37:59 +0200 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-08-10 21:32:28 +0200 |
| commit | 016f8ffc48cb01d1e7701649c728c5d2e737d295 (patch) | |
| tree | 121eb51e535dc7ea6aafd2fcb741f02d7c47b414 /kernel/trace/trace_clock.c | |
| parent | tracing: Fix synchronizing to event changes with tracepoint_synchronize_unreg... (diff) | |
| download | linux-016f8ffc48cb01d1e7701649c728c5d2e737d295.tar.xz linux-016f8ffc48cb01d1e7701649c728c5d2e737d295.zip | |
uprobes: Use synchronize_rcu() not synchronize_sched()
While debugging another bug, I was looking at all the synchronize*()
functions being used in kernel/trace, and noticed that trace_uprobes was
using synchronize_sched(), with a comment to synchronize with
{u,ret}_probe_trace_func(). When looking at those functions, the data is
protected with "rcu_read_lock()" and not with "rcu_read_lock_sched()". This
is using the wrong synchronize_*() function.
Link: http://lkml.kernel.org/r/20180809160553.469e1e32@gandalf.local.home
Cc: stable@vger.kernel.org
Fixes: 70ed91c6ec7f8 ("tracing/uprobes: Support ftrace_event_file base multibuffer")
Acked-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_clock.c')
0 files changed, 0 insertions, 0 deletions