lkml.org 
[lkml]   [2014]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [GIT PULL] x86/kaslr for v3.14
From
Date
On Tue, 2014-01-28 at 16:08 -0500, Dave Jones wrote: 
> On Tue, Jan 28, 2014 at 12:25:15PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 28, 2014 at 12:15 PM, Borislav Petkov <bp@alien8.de> wrote:
> > >
> > > Shouldn't we hold that down in the Kconfig help text of DEBUG_INFO?
> > > Something like:
> > >
> > > "You don't need to enable this if you want symbolic names for kernel
> > > objects. Enable CONFIG_KALLSYMS instead."
> >
> > Probably. And then we should make sure that allyesconfig/allmodconfig
> > don't pick it.
> >
> > There *are* reasonable uses for DEBUG_INFO:
> >
> > - if you very actively and extensively use kgdb, DEBUG_INFO is very useful.
> >
> > - distros might want to build distro kernels with DEBUG_INFO for the
> > kernel debug package
>
> - objdump -S is kind of useful. I find myself using that quite often.
> (like at least a dozen times each merge window)

For those with wimpy asm muscles (/me), it's very useful indeed, as are
gdb list *foo()+0x10 or *0xfeedbabedeadbeef. I always build with full
DEBUG_INFO, just keep configs lean enough that lots of kernels fit in a
2G /boot, and _never ever_ set a box up with a microscopic root.

> pretty sure it works with DEBUG_INFO_REDUCED though, which is somewhat
> faster than full DEBUG_INFO

Yeah, it does.

-Mike



\
 
 \ /
  Last update: 2014-01-29 07:41    [W:0.129 / U:1.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site