Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753629AbaJASFT (ORCPT ); Wed, 1 Oct 2014 14:05:19 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:44093 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751780AbaJASFS (ORCPT ); Wed, 1 Oct 2014 14:05:18 -0400 Date: Wed, 1 Oct 2014 11:05:10 -0700 From: josh@joshtriplett.org To: Andy Lutomirski Cc: Rob Landley , frowand.list@gmail.com, Andrew Morton , "linux-kernel@vger.kernel.org" , Chuck Ebbert , Randy Dunlap , Shuah Khan Subject: Re: [PATCH v5] init: Disable defaults if init= fails Message-ID: <20141001180510.GA28540@cloud> References: <5c6381879bea68aebb13530442f1cf8a052be97f.1411958379.git.luto@amacapital.net> <542B4DA3.5080105@gmail.com> <542B519B.6010001@landley.net> <542B5E44.40303@gmail.com> <542B7200.6030902@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 30, 2014 at 09:53:56PM -0700, Andy Lutomirski wrote: > I significantly prefer default N. Scripts that play with init= really > don't want the fallback, and I can imagine contexts in which it could > be a security problem. While I certainly would prefer the non-fallback behavior for init as well, standard kernel practice has typically been to use "default y" for previously built-in features that become configurable. And I'd certainly prefer a compile-time configuration option like this (even with default y) over a "strictinit" kernel command-line option. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/