Commit 933ff9f2 authored Nov 12, 2014 by Luis Claudio R. Goncalves Committed by Steven Rostedt Nov 13, 2014

tracing: Fix traceoff_on_warning handling on boot command line

According to the documentation, adding "traceoff_on_warning" to the boot
command line should be enough to enable the feature. But right now it is
necessary to specify "traceoff_on_warning=". Along with fixing that, also
verify if the value passed, if any, is either "0" or "off".

Link: http://lkml.kernel.org/r/20141112231400.GL12281@uudg.org

Signed-off-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

parent fe578ba3

kernel/trace/trace.c

+3 −2

Original line number	Original line	Diff line number	Diff line
	@@ -155,10 +155,11 @@ __setup("ftrace_dump_on_oops", set_ftrace_dump_on_oops);

	static int __init stop_trace_on_warning(char *str)		static int __init stop_trace_on_warning(char *str)
	{		{
			if ((strcmp(str, "=0") != 0 && strcmp(str, "=off") != 0))
	__disable_trace_on_warning = 1;		__disable_trace_on_warning = 1;
	return 1;		return 1;
	}		}
	__setup("traceoff_on_warning=", stop_trace_on_warning);		__setup("traceoff_on_warning", stop_trace_on_warning);

	static int __init boot_alloc_snapshot(char *str)		static int __init boot_alloc_snapshot(char *str)
	{		{