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]
Date:	Thu, 28 Jan 2016 10:55:57 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [RFC][BUG] tracer: Fails to work

On Thu, 28 Jan 2016 16:29:57 +0100
Peter Zijlstra <peterz@...radead.org> wrote:

> On Thu, Jan 28, 2016 at 02:53:53PM +0000, Mathieu Desnoyers wrote:
> > On x86, many BIOS wipe the memory content even after a warm reset :(
> > The most reliable solution I found on x86 is to use kexec() to
> > boot into a new kernel, mount the DAX filesystem again and read the
> > buffers from there.  
> 
> kexec() is tricky when the kernel is still prefectly fine, I doubt it'll
> work when I've hosed it properly :/

I use it all the time when a kernel crashes. Well, kexec and kdump.
Which by the way, the crash utility has a way to read the ftrace ring
buffer from a kexec kdump core file.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ