linux-kernel - Re: [RFC] improve_stack: make stack dump output useful again

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:	Thu, 13 Mar 2014 19:12:27 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Sasha Levin <sasha.levin@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	keescook@...omium.org
Subject: Re: [RFC] improve_stack: make stack dump output useful again

On Thu, Mar 13, 2014 at 03:03:41PM -0700, Linus Torvalds wrote:

 > You need to look at the *symbol* number. In this output:
 > 
 >      [<ffffffff810020c2>] do_one_initcall+0xc2/0x1e0
 > 
 > that "ffffffff810020c2" is crap, and is going away. The address that
 > is meaningful and valid is the "do_one_initcall+0xc2" part.
 > 
 > *That* is the part you'd use to parse in user space.
 > 
 > Try it today with the CONFIG_RANDOMIZE_BASE option to see. Using the
 > hex number doesn't *work*.

That reminds me, perf top is still busted when this option is enabled.

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