diff options
author | Masami Hiramatsu <mhiramat@kernel.org> | 2018-11-05 18:04:01 +0900 |
---|---|---|
committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-12-08 20:54:10 -0500 |
commit | 0e2b81f7b52a1c1a8c46986f9ca01eb7b3c421f8 (patch) | |
tree | 97f5c8d9e589e25b2799d559a8ab5130dd05a8d4 /kernel/trace/fgraph.c | |
parent | 7bbab38d07f3185fddf6fce126e2239010efdfce (diff) | |
download | linux-0e2b81f7b52a1c1a8c46986f9ca01eb7b3c421f8.tar.gz linux-0e2b81f7b52a1c1a8c46986f9ca01eb7b3c421f8.tar.bz2 linux-0e2b81f7b52a1c1a8c46986f9ca01eb7b3c421f8.zip |
tracing: Remove unneeded synth_event_mutex
Rmove unneeded synth_event_mutex. This mutex protects the reference
count in synth_event, however, those operational points are already
protected by event_mutex.
1. In __create_synth_event() and create_or_delete_synth_event(),
those synth_event_mutex clearly obtained right after event_mutex.
2. event_hist_trigger_func() is trigger_hist_cmd.func() which is
called by trigger_process_regex(), which is a part of
event_trigger_regex_write() and this function takes event_mutex.
3. hist_unreg_all() is trigger_hist_cmd.unreg_all() which is called
by event_trigger_regex_open() and it takes event_mutex.
4. onmatch_destroy() and onmatch_create() have long call tree,
but both are finally invoked from event_trigger_regex_write()
and event_trace_del_tracer(), former takes event_mutex, and latter
ensures called under event_mutex locked.
Finally, I ensured there is no resource conflict. For safety,
I added lockdep_assert_held(&event_mutex) for each function.
Link: http://lkml.kernel.org/r/154140864134.17322.4796059721306031894.stgit@devbox
Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Tested-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/fgraph.c')
0 files changed, 0 insertions, 0 deletions