linux-kernel - Re: [RFC][PATCH] tracing: Disable tracing on warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130617183206.GB3204@twins.programming.kicks-ass.net>
Date:	Mon, 17 Jun 2013 20:32:06 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][PATCH] tracing: Disable tracing on warning

On Mon, Jun 17, 2013 at 12:42:55PM -0400, Steven Rostedt wrote:
> Add a traceoff_on_warning option in both the kernel command line as well
> as a sysctl option. When set, any WARN*() function that is hit will cause
> the tracing_on variable to be cleared, which disables writing to the
> ring buffer.
> 
> This is useful especially when tracing a bug with function tracing. When
> a warning is hit, the print caused by the warning can flood the trace with
> the functions that producing the output for the warning. This can make the
> resulting trace useless by either hiding where the bug happened, or worse,
> by overflowing the buffer and losing the trace of the bug totally.
> 
> Signed-off-by: Steven Rostedt <rostedt@...dmis.org>

Neat;

Acked-by: Peter Zijlstra <peterz@...radead.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/