aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/trace-event-scripting.c
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <[email protected]>2013-07-23 22:21:59 -0400
committerSteven Rostedt <[email protected]>2013-07-26 08:57:32 -0400
commit09d8091c024ec88d1541d93eb8ddb2bd5cf10c39 (patch)
tree170740cc6580d2d397744006f4c3ec545aea497f /tools/perf/util/trace-event-scripting.c
parent195a8afc7ac962f8da795549fe38e825f1372b0d (diff)
tracing: Remove locking trace_types_lock from tracing_reset_all_online_cpus()
Commit a82274151af "tracing: Protect ftrace_trace_arrays list in trace_events.c" added taking the trace_types_lock mutex in trace_events.c as there were several locations that needed it for protection. Unfortunately, it also encapsulated a call to tracing_reset_all_online_cpus() which also takes the trace_types_lock, causing a deadlock. This happens when a module has tracepoints and has been traced. When the module is removed, the trace events module notifier will grab the trace_types_lock, do a bunch of clean ups, and also clears the buffer by calling tracing_reset_all_online_cpus. This doesn't happen often which explains why it wasn't caught right away. Commit a82274151af was marked for stable, which means this must be sent to stable too. Link: http://lkml.kernel.org/r/[email protected] Reported-by: Arend van Spril <[email protected]> Tested-by: Arend van Spriel <[email protected]> Cc: Alexander Z Lam <[email protected]> Cc: Vaibhav Nagarnaik <[email protected]> Cc: David Sharp <[email protected]> Cc: [email protected] # 3.10 Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions