[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140128210857.GA1377@redhat.com>
Date: Tue, 28 Jan 2014 16:08:57 -0500
From: Dave Jones <davej@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Richard Weinberger <richard@....at>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Kees Cook <keescook@...omium.org>,
Cong Ding <dinggnu@...il.com>, Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mathias Krause <minipli@...glemail.com>,
Michael Davidson <md@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Wei Yongjun <yongjun_wei@...ndmicro.com.cn>
Subject: Re: [GIT PULL] x86/kaslr for v3.14
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@...en8.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)
pretty sure it works with DEBUG_INFO_REDUCED though, which is somewhat
faster than full DEBUG_INFO
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