| 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
| ||
|
Message-ID: <20081103081416.GB28771@elte.hu> Date: Mon, 3 Nov 2008 09:14:16 +0100 From: Ingo Molnar <mingo@...e.hu> To: Steven Rostedt <rostedt@...dmis.org> Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer] * Steven Rostedt <rostedt@...dmis.org> wrote: > > 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> applied to tip/tracing/ftrace, thanks guys! Ingo -- 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/
Powered by blists - more mailing lists