• A
    init: allow CONFIG_INIT_FALLBACK=n to disable defaults if init= fails · 6ef4536e
    Andy Lutomirski 提交于
    If a user puts init=/whatever on the command line and /whatever can't be
    run, then the kernel will try a few default options before giving up.  If
    init=/whatever came from a bootloader prompt, then this is unexpected but
    probably harmless.  On the other hand, if it comes from a script (e.g.  a
    tool like virtme or perhaps a future kselftest script), then the fallbacks
    are likely to exist, but they'll do the wrong thing.  For example, they
    might unexpectedly invoke systemd.
    
    This adds a config option CONFIG_INIT_FALLBACK.  If unset, then a failure
    to run the specified init= process be fatal.
    
    The tentative plan is to remove CONFIG_INIT_FALLBACK for 3.20.
    
    [akpm@linux-foundation.org: coding-style fixes]
    Signed-off-by: NAndy Lutomirski <luto@amacapital.net>
    Cc: Rob Landley <rob@landley.net>
    Cc: Chuck Ebbert <cebbert.lkml@gmail.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Shuah Khan <shuah.kh@samsung.com>
    Cc: Frank Rowand <frowand.list@gmail.com>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Acked-by: NRusty Russell <rusty@rustcorp.com.au>
    Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
    6ef4536e
Kconfig 64.2 KB