aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorSteven Rostedt <[email protected]>2012-06-05 19:28:14 +0900
committerSteven Rostedt <[email protected]>2012-07-31 10:29:55 -0400
commit72ef3794c5cd5f5f0e6355c24a529224c449cd14 (patch)
tree3c8c4bb28009aa938c9e24b33914d11852ec4712 /tools/perf/util/scripting-engines/trace-event-python.c
parent647664eaf4033501739ac1f42dd52ce8c9266ccc (diff)
kprobes: Inverse taking of module_mutex with kprobe_mutex
Currently module_mutex is taken before kprobe_mutex, but this can cause issues when we have kprobes register ftrace, as the ftrace mutex is taken before enabling a tracepoint, which currently takes the module mutex. If module_mutex is taken before kprobe_mutex, then we can not have kprobes use the ftrace infrastructure. There seems to be no reason that the kprobe_mutex can't be taken before the module_mutex. Running lockdep shows that it is safe among the kernels I've run. Link: http://lkml.kernel.org/r/[email protected] Cc: Thomas Gleixner <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: "H. Peter Anvin" <[email protected]> Cc: Ananth N Mavinakayanahalli <[email protected]> Cc: "Frank Ch. Eigler" <[email protected]> Cc: Andrew Morton <[email protected]> Cc: Frederic Weisbecker <[email protected]> Cc: Masami Hiramatsu <[email protected]> Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions