On Fri, 21 Feb 2014 13:18:26 -0800 "H. Peter Anvin" <[email protected]> wrote:
> On 02/21/2014 01:15 PM, Andrew Morton wrote: > >> > >> I've been slapped down for adding more config options in the past, and > >> I think it's unlikely that people using CONFIG_RANDOMIZE_BASE won't > >> want the modules base randomized too. I think this is a safe default, > >> but if you see it as a requirement, I can change it. > > > > I think there were issues with some embedded systems where it's > > hard/impossible to provide/alter boot parameters. > > > > We now allow kernel parameters to be compiled into the kernel image for > that reason. We do? What's that Kconfig variable called? We have a few (inconsistently named) things like CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=1 CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1 CONFIG_BOOTPARAM_HUNG_TASK_PANIC=y CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=1 CONFIG_DEBUG_BOOT_PARAMS=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1 CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 which presumably become obsolete with a general feed-this-string-to-the-kernel feature? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
