lkml.org 
[lkml]   [2014]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [RFC] improve_stack: make stack dump output useful again
From
On Thu, Mar 13, 2014 at 4:12 PM, Dave Jones <davej@redhat.com> wrote:
> 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.

Hrm, works for me. I'm not very familiar with what to expect, but
comparing output between kaslr boot and nokaslr boot, it looks the
same to me.

-Kees

--
Kees Cook
Chrome OS Security


\
 
 \ /
  Last update: 2014-03-14 20:01    [W:0.105 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site