tracing: Allow histogram triggers to access ftrace internal events
authorSteven Rostedt (VMware) <rostedt@goodmis.org>
Thu, 10 May 2018 16:42:10 +0000 (12:42 -0400)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Tue, 29 May 2018 12:29:22 +0000 (08:29 -0400)
Now that trace_marker can have triggers, including a histogram triggers, the
onmatch() and onmax() access the trace event. To do so, the search routine
to find the event file needs to use the raw __find_event_file() that does
not filter out ftrace events.

Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/trace_events_hist.c

index b9061ed59bbd9faabc7da7a65ae959a89e4b689f..046c716a6536ba4f504df2523a420b92920d4e52 100644 (file)
@@ -2865,7 +2865,7 @@ static struct trace_event_file *event_file(struct trace_array *tr,
 {
        struct trace_event_file *file;
 
-       file = find_event_file(tr, system, event_name);
+       file = __find_event_file(tr, system, event_name);
        if (!file)
                return ERR_PTR(-EINVAL);