lkml.org 
[lkml]   [2014]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 3.15 102/122] tracing: Remove ftrace_stop/start() from reading the trace file
    Date
    3.15-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>

    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>

    ---
    kernel/trace/trace.c | 2 --
    1 file changed, 2 deletions(-)

    --- a/kernel/trace/trace.c
    +++ b/kernel/trace/trace.c
    @@ -1367,7 +1367,6 @@ void tracing_start(void)

    arch_spin_unlock(&ftrace_max_lock);

    - ftrace_start();
    out:
    raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
    }
    @@ -1414,7 +1413,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;



    \
     
     \ /
      Last update: 2014-07-08 02:21    [W:4.328 / U:0.228 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site