summaryrefslogtreecommitdiff
path: root/kernel/params.c
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2010-03-13 03:56:00 +0300
committerSteven Rostedt <rostedt@goodmis.org>2010-03-13 04:30:21 +0300
commita2f8071428ed9a0f06865f417c962421c9a6b488 (patch)
tree731d1e4f684fa5e5e27b56f1ed5f74d5945b20bd /kernel/params.c
parent283740c619d211e34572cc93c8cdba92ccbdb9cc (diff)
downloadlinux-a2f8071428ed9a0f06865f417c962421c9a6b488.tar.xz
tracing: Disable buffer switching when starting or stopping trace
When the trace iterator is read, tracing_start() and tracing_stop() is called to stop tracing while the iterator is processing the trace output. These functions disable both the standard buffer and the max latency buffer. But if the wakeup tracer is running, it can switch these buffers between the two disables: buffer = global_trace.buffer; if (buffer) ring_buffer_record_disable(buffer); <<<--------- swap happens here buffer = max_tr.buffer; if (buffer) ring_buffer_record_disable(buffer); What happens is that we disabled the same buffer twice. On tracing_start() we can enable the same buffer twice. All ring_buffer_record_disable() must be matched with a ring_buffer_record_enable() or the buffer can be disable permanently, or enable prematurely, and cause a bug where a reset happens while a trace is commiting. This patch protects these two by taking the ftrace_max_lock to prevent a switch from occurring. Found with Li Zefan's ftrace_stress_test. Cc: stable@kernel.org Reported-by: Lai Jiangshan <laijs@cn.fujitsu.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/params.c')
0 files changed, 0 insertions, 0 deletions