linux-kernel - Re: [PATCH] ftrace: ftrace_dump_on

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:	Sat, 1 Nov 2008 15:13:32 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
cc:	Ingo Molnar <mingo@...e.hu>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer]


On Sat, 1 Nov 2008, Peter Zijlstra wrote:

> On Sat, 2008-11-01 at 14:43 -0400, Steven Rostedt wrote:
> > On Sat, 1 Nov 2008, Peter Zijlstra wrote:
> > 
> > > seems useful to debug crashes that happen before I read userspace.
> > 
> > Hmm, I think it might be better to separate this from the dump_on_oops.
> > How about a ftrace_default_tracer parameter?
> > 
> > If one is defined, it is activated as soon as it is initialized. This way 
> > we decouple the dump_on_oops, which we may not always want, and a way to 
> > start tracers before the switch to user space.
> 
> Like so?

Sure.

> 
> ---
> Subject: ftrace: enable setting an ftrace tracer on boot
> 
> In order to facilitate early boot trouble, allow one to specify a tracer
> on the kernel boot line.
> 
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>

Acked-by: Steven Rostedt <srostedt@...hat.com>

-- Steve
--
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/