[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140314183349.GA3889@redhat.com>
Date: Fri, 14 Mar 2014 14:33:49 -0400
From: Dave Jones <davej@...hat.com>
To: Kees Cook <keescook@...omium.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Sasha Levin <sasha.levin@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] improve_stack: make stack dump output useful again
On Fri, Mar 14, 2014 at 11:31:11AM -0700, Kees Cook wrote:
> On Thu, Mar 13, 2014 at 4:12 PM, Dave Jones <davej@...hat.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.
I don't get kernel symbols resolved at all when it's enabled
Disabling the config option makes them come back again.
I didn't try nokaslr.
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/
Powered by blists - more mailing lists