Linus, This includes three fixes. Two fix features added in 3.9 and one fixes a long time minor bug.
The first patch fixes a race that can happen if the user switches
from the irqsoff tracer to another tracer. If a irqs off latency is
detected, it will try to use the snapshot buffer, but the new tracer
wont have it allocated. There's a nasty warning that gets printed and
the trace is ignored. Nothing crashes, just a nasty WARN_ON is shown.
The second patch fixes an issue where if the sysctl is used to disable
and enable function tracing, it can put the function tracing into an
unstable state.
The third patch fixes an issue with perf using the function tracer.
An update was done, where the stub function could be called during
the perf function tracing, and that stub function wont have the
"control" flag set and cause a nasty warning when running perf.
Please pull the latest trace-fixes-3.9-rc6 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-fixes-3.9-rc6
Head SHA1: 620bd150ec911fae0ad02e66fa003548505ec7f4
Jan Kiszka (1):
ftrace: Consistently restore trace function on sysctl enabling
Steven Rostedt (Red Hat) (2):
tracing: Fix race with update_max_tr_single and changing tracers
ftrace: Do not call stub functions in control loop
----
include/linux/ftrace.h | 2 ++
kernel/trace/ftrace.c | 13 +++++--------
kernel/trace/trace.c | 5 ++++-
3 files changed, 11 insertions(+), 9 deletions(-)
signature.asc
Description: This is a digitally signed message part
