From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Le Goater Subject: Re: [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2) Date: Mon, 29 Oct 2007 11:13:42 +0100 Message-ID: <4725B256.3020807@fr.ibm.com> References: <20071027002448.GH30533@stusta.de> <4724B4F2.7070500@goop.org> <20071028170008.GD7227@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "Eric W. Biederman" Cc: Adrian Bunk , Jeremy Fitzhardinge , Kir Kolyshkin , containers@lists.osdl.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, kir@openvz.org List-Id: containers.vger.kernel.org Eric W. Biederman wrote: > Adrian Bunk writes: > >> On Sun, Oct 28, 2007 at 09:12:34AM -0700, Jeremy Fitzhardinge wrote: >>> Eric W. Biederman wrote: >>>> Roughly that sounds like CONFIG_EXPERIMENTAL to me. But I would >>>> be happy to hear if someone has a better idea. >>> Rather than overload an existing config option, why not add one with the >>> specific semantics you want: CONFIG_UNSTABLE_UABI. The problem seems >>> like one which which may occur again, though one hopes not too often. I >>> guess the risk is that people will leave their subsystems depending on >>> it permanently (sysfs?), so it ends up being set all the time and >>> becomes as useless as EXPERIMENTAL... >> Then let SYSFS depend on UNSTABLE_UABI for the next 10 years and we have >> an excuse for breaking the ABI with each new kernel... >> >> Either the ABI is stable or it should not be exposed to users at all. > > If we need a new config for it. CONFIG_IMMATURE is the closest I > can think of. Pavel also has a CONFIG_NAMESPACES patch that he should be resending to andrew when 2.6.24-rc1-mm1 is released. pidns will go under this option, like all the other namespaces, and should protect the distros from shipping any immature namespace. C.