linux-kernel - Re: [PATCH] tracing: Dump either the oops's cpu source or all cpus buffers

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 18 Apr 2010 21:19:00 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	fweisbec@...il.com
Cc:	rostedt@...dmis.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
	tglx@...utronix.de, lizf@...fujitsu.com, laijs@...fujitsu.com
Subject: Re: [PATCH] tracing: Dump either the oops's cpu source or all cpus
 buffers

From: Frederic Weisbecker <fweisbec@...il.com>
Date: Sun, 18 Apr 2010 22:50:10 +0200

> The ftrace_dump_on_oops kernel parameter, sysctl and sysrq let one
> dump every cpu buffers when an oops or panic happens.
> 
> It's nice when you have few cpus but it may take ages if have many,
> plus you miss the real origin of the problem in all the cpu traces.
> 
> Sometimes, all you need is to dump the cpu buffer that triggered the
> opps, most of the time it is our main interest.
> 
> This patch modifies ftrace_dump_on_oops to handle this choice.
> 
> The ftrace_dump_on_oops kernel parameter, when it comes alone, has
> the same behaviour than before. But ftrace_dump_on_oops=orig_cpu
> will only dump the buffer of the cpu that oops'ed.
> 
> Similarly, sysctl kernel.ftrace_dump_on_oops=1 and
> echo 1 > /proc/sys/kernel/ftrace_dump_on_oops keep their previous
> behaviour. But setting 2 jumps into cpu origin dump mode.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>

Thanks I was trying to figure out a way to make ftrace dump
do exactly this over the past few days :-)

Acked-by: David S. Miller <davem@...emloft.net>
--
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/