summaryrefslogtreecommitdiff
path: root/kernel
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2014-06-24 23:50:09 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-07-09 11:18:28 -0700
commit1857a6278161211c4247041747a906da505018d3 (patch)
tree3d835e22a35692b58d6e6043faedce75d3813f8a /kernel
parent1d58e36ff8741e847d06fdc2fc1a27f313861944 (diff)
downloadkernel-common-1857a6278161211c4247041747a906da505018d3.tar.gz
kernel-common-1857a6278161211c4247041747a906da505018d3.tar.bz2
kernel-common-1857a6278161211c4247041747a906da505018d3.zip
tracing: Remove ftrace_stop/start() from reading the trace file
commit 099ed151675cd1d2dbeae1dac697975f6a68716d upstream. Disabling reading and writing to the trace file should not be able to disable all function tracing callbacks. There's other users today (like kprobes and perf). Reading a trace file should not stop those from happening. Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/trace/trace.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index f0831c22760c..fd21e601a891 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1355,7 +1355,6 @@ void tracing_start(void)
arch_spin_unlock(&ftrace_max_lock);
- ftrace_start();
out:
raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
}
@@ -1402,7 +1401,6 @@ void tracing_stop(void)
struct ring_buffer *buffer;
unsigned long flags;
- ftrace_stop();
raw_spin_lock_irqsave(&global_trace.start_lock, flags);
if (global_trace.stop_count++)
goto out;