]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
tracing: Disable trace_printk buffer on warning too
authorSteven Rostedt <rostedt@goodmis.org>
Wed, 21 Jan 2026 14:38:58 +0000 (09:38 -0500)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Mon, 26 Jan 2026 22:45:17 +0000 (17:45 -0500)
commit6bdf07302f42783345289caec7d91fa364e013ec
treecd88ed6bbddca7fd34f3c84b2af423065a7f0482
parenta9e0c5897a787751c373812ea21fabf955625b34
tracing: Disable trace_printk buffer on warning too

When /proc/sys/kernel/traceoff_on_warning is set to 1, the top level
tracing buffer is disabled when a warning happens. This is very useful
when debugging and want the tracing buffer to stop taking new data when a
warning triggers keeping the events that lead up to the warning from being
overwritten.

Now that there is also a persistent ring buffer and an option to have
trace_printk go to that buffer, the same holds true for that buffer. A
warning could happen just before a crash but still write enough events to
lose the events that lead up to the first warning that was the reason for
the crash.

When /proc/sys/kernel/traceoff_on_warning is set to 1 and a warning is
triggered, not only disable the top level tracing buffer, but also disable
the buffer that trace_printk()s are written to.

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Link: https://patch.msgid.link/20260121093858.5c5d7e7b@gandalf.local.home
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace.c