Date: Sat, 26 Feb 2005 02:31:37 +0100
From: Andrea Arcangeli <andrea@cpushare.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] seccomp: don't say it was more or less mandatory
Message-ID: <20050226013137.GO20715@opteron.random>
References: <20050223014233.6710fd73.akpm@osdl.org> <20050224215136.GK8651@stusta.de> <20050224224134.GE20715@opteron.random> <20050225211453.GC3311@stusta.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050225211453.GC3311@stusta.de>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1407
Lines: 30

On Fri, Feb 25, 2005 at 10:14:54PM +0100, Adrian Bunk wrote:
> You don't need this feature unless you know you need it.

But you may not know that you need it since in the help text I
intentionally didn't mention which software requires the option to be
set to Y (I didn't mention it, since I didn't want to use the kernel
configuration help text to get free advertisement, but OTOH if people is
unsure while they configure the kernel I certainly prefer that they set
it to Y ;).

> It's not about risk or the actual size of the code - there are many 
> small or big features in the kernel that might be useful under some 
> circumstances, but even the IPv6 help text still suggests to say N
> to IPv6.

IPV6 is some relevant amount of code and complexity, seccomp is only a
few bytes and very simple, it's not even a kbyte of ram that you're
paying if you enable it. Only embedded cares about bytes, and that's why
the option exists for embedded.

One thing I'm concerned about (more than the "Y" in the help text) is
that the distributions will enable the option in their binary kernel
images. I hope they will given it's only a matter of a few bytes.

Thanks.
-
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/