summaryrefslogtreecommitdiffstats
path: root/block/blk-timeout.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-04-08 15:14:11 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2013-04-08 15:14:11 -0700
commit5f2f280f87fe9755dba915f1ade149840885fd91 (patch)
tree31c8564dfd1fcb0ea0023a23c3aefd8108d7b2de /block/blk-timeout.c
parent31880c37c11e28cb81c70757e38392b42e695dc6 (diff)
parent395b97a3aeff0b8d949ee3e67bf8c11c5ffd6861 (diff)
Merge tag 'trace-fixes-3.9-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "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." * tag 'trace-fixes-3.9-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: ftrace: Do not call stub functions in control loop ftrace: Consistently restore trace function on sysctl enabling tracing: Fix race with update_max_tr_single and changing tracers
Diffstat (limited to 'block/blk-timeout.c')
0 files changed, 0 insertions, 0 deletions