Linus, The clean up patch commit 0fb9656d "tracing: Make tracing_enabled be equal to tracing_on" caused two regressions.
1) The irqs off latency tracer no longer starts if tracing_on is off
when the tracer is set, and then tracing_on is enabled. The tracing_on
file needs the hook that tracing_enabled had to enable tracers if they
request it (call the tracer's start() method).
2) That commit had a separate change that really should have been a
separate patch, but it must have been added accidently with the -a
option of git commit. But as the change is still related to the commit
it wasn't noticed in review. That change, changed the way blocking is
done by the trace_pipe file with respect to the tracing_on settings.
I've been told that this change breaks current userspace, and this
specific change is being reverted.
Please pull trace-3.8-rc3-regression-fix, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-3.8-rc3-regression-fix
Head SHA1: 84c630600dc007d2fbd307088b87c9be85b40a97
Liu Bo (1):
tracing: Fix regression of trace_pipe
Steven Rostedt (1):
tracing: Fix regression with irqsoff tracer and tracing_on file
----
kernel/trace/trace.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
signature.asc
Description: This is a digitally signed message part
