Messages in this thread | | | Date | Tue, 28 Jan 2014 12:25:15 -0800 | Subject | Re: [GIT PULL] x86/kaslr for v3.14 | From | Linus Torvalds <> |
| |
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
but for most kernel developers, DEBUG_INFO really just bloats things and makes the build much *much* slower, for very little gain. Sure, you get line numbers, but let's face it, it's not that hard to just do "x/20i <address>" and trying to match it up with the generated code instead. And since "just match it up" model works with user-reported oopses of random kernels, you had better be able and willing to do that *anyway*.
If most of the oopses you decode are on your own machine with your own kernel, you might want to try to learn to be more careful when writing code. And I'm not even kidding.
Linus
| |