diff options
author | Oleg Nesterov <oleg@redhat.com> | 2013-07-29 19:50:33 +0200 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2013-07-31 19:12:48 +0200 |
commit | 2816c551c796ec14620325b2c9ed75b9979d3125 (patch) | |
tree | c4bc262514de5ef265001411bcdf7ad65916eae9 /Makefile | |
parent | debugfs: debugfs_remove_recursive() must not rely on list_empty(d_subdirs) (diff) | |
download | linux-2816c551c796ec14620325b2c9ed75b9979d3125.tar.xz linux-2816c551c796ec14620325b2c9ed75b9979d3125.zip |
tracing: trace_remove_event_call() should fail if call/file is in use
Change trace_remove_event_call(call) to return the error if this
call is active. This is what the callers assume but can't verify
outside of the tracing locks. Both trace_kprobe.c/trace_uprobe.c
need the additional changes, unregister_trace_probe() should abort
if trace_remove_event_call() fails.
The caller is going to free this call/file so we must ensure that
nobody can use them after trace_remove_event_call() succeeds.
debugfs should be fine after the previous changes and event_remove()
does TRACE_REG_UNREGISTER, but still there are 2 reasons why we need
the additional checks:
- There could be a perf_event(s) attached to this tp_event, so the
patch checks ->perf_refcount.
- TRACE_REG_UNREGISTER can be suppressed by FTRACE_EVENT_FL_SOFT_MODE,
so we simply check FTRACE_EVENT_FL_ENABLED protected by event_mutex.
Link: http://lkml.kernel.org/r/20130729175033.GB26284@redhat.com
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions