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  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:	Mon, 04 Jan 2010 08:24:53 +0900
From:	Tejun Heo <>
To:	Arjan van de Ven <>
CC:	Hui Zhu <>,
	Russell King <>,
	saeed bishara <>,
	Catalin Marinas <>,
	Nicolas Pitre <>,
	Ralf Baechle <>,
	David Daney <>,
	Tomaso Paoletti <>,
	Chris Dearman <>,
	Paul Gortmaker <>,
	Thomas Gleixner <>,
	Ingo Molnar <>,
	"H. Peter Anvin" <>,,
	Frederic Weisbecker <>,
	Alexey Dobriyan <>,
	Brian Gerst <>,
	Rusty Russell <>,
	Andrew Morton <>,
	Steven Rostedt <>,
	Greg Kroah-Hartman <>,
	"Paul E. McKenney" <>,,,, Coly Li <>
Subject: Re: [PATCH] stack2core: show stack message and convert it to core
 file 	when kernel die

On 01/04/2010 08:14 AM, Arjan van de Ven wrote:
>> Whichever one works but s2c wouldn't require symbol decoding.  Maybe
>> we can simply add an option to tell it to just parse the oops and
>> output it in machine friendly format.  Oh, also, the patch does add
>> new information the module load addresses.  We should be able to add
>> those to the oops message in a compact form.
> actually one does not need those; you know the start address of the
> function already from the current oops output, and since you know the
> address of the function within the module as well, you know the start
> address of the module.

Right.  Thanks for the explanation.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists