[PATCH 4.4 04/41] tracing: Fix trace_pipe behavior for instance traces
From: Greg Kroah-Hartman
Date: Tue Oct 03 2017 - 08:22:00 EST
4.4-stable review patch. If anyone has any objections, please let me know.
From: Tahsin Erdogan <tahsin@xxxxxxxxxx>
commit 75df6e688ccd517e339a7c422ef7ad73045b18a2 upstream.
When reading data from trace_pipe, tracing_wait_pipe() performs a
check to see if tracing has been turned off after some data was read.
Currently, this check always looks at global trace state, but it
should be checking the trace instance where trace_pipe is located at.
Because of this bug, cat instances/i1/trace_pipe in the following
script will immediately exit instead of waiting for data:
echo 0 > tracing_on
mkdir -p instances/i1
echo 1 > instances/i1/tracing_on
echo 1 > instances/i1/events/sched/sched_process_exec/enable
Fixes: 10246fa35d4f ("tracing: give easy way to clear trace buffer")
Signed-off-by: Tahsin Erdogan <tahsin@xxxxxxxxxx>
Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
kernel/trace/trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -4701,7 +4701,7 @@ static int tracing_wait_pipe(struct file
* iter->pos will be 0 if we haven't read anything.
- if (!tracing_is_on() && iter->pos)
+ if (!tracer_tracing_is_on(iter->tr) && iter->pos)