diff options
| author | Steven Rostedt (VMware) <[email protected]> | 2018-08-09 15:37:59 -0400 |
|---|---|---|
| committer | Steven Rostedt (VMware) <[email protected]> | 2018-08-10 15:32:28 -0400 |
| commit | 016f8ffc48cb01d1e7701649c728c5d2e737d295 (patch) | |
| tree | 121eb51e535dc7ea6aafd2fcb741f02d7c47b414 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | e0a568dcd18bdaa77877d558700ce4d3bbbb12b8 (diff) | |
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/[email protected]
Cc: [email protected]
Fixes: 70ed91c6ec7f8 ("tracing/uprobes: Support ftrace_event_file base multibuffer")
Acked-by: Oleg Nesterov <[email protected]>
Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions