Browse Source

tracing: Remove ftrace_stop/start() from reading the trace file

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.

Cc: stable@vger.kernel.org # 3.0+
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Steven Rostedt (Red Hat) 11 years ago
parent
commit
099ed15167
1 changed files with 0 additions and 2 deletions
  1. 0 2
      kernel/trace/trace.c

+ 0 - 2
kernel/trace/trace.c

@@ -1396,7 +1396,6 @@ void tracing_start(void)
 
 
 	arch_spin_unlock(&global_trace.max_lock);
 	arch_spin_unlock(&global_trace.max_lock);
 
 
-	ftrace_start();
  out:
  out:
 	raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
 	raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
 }
 }
@@ -1443,7 +1442,6 @@ void tracing_stop(void)
 	struct ring_buffer *buffer;
 	struct ring_buffer *buffer;
 	unsigned long flags;
 	unsigned long flags;
 
 
-	ftrace_stop();
 	raw_spin_lock_irqsave(&global_trace.start_lock, flags);
 	raw_spin_lock_irqsave(&global_trace.start_lock, flags);
 	if (global_trace.stop_count++)
 	if (global_trace.stop_count++)
 		goto out;
 		goto out;