public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg@fr.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Kir Kolyshkin <kir@swsoft.com>,
	containers@lists.osdl.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	kir@openvz.org
Subject: Re: [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2)
Date: Mon, 29 Oct 2007 11:13:42 +0100	[thread overview]
Message-ID: <4725B256.3020807@fr.ibm.com> (raw)
In-Reply-To: <m13avvqef1.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> Adrian Bunk <bunk@kernel.org> 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.

  reply	other threads:[~2007-10-29 10:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CBC546DD07068244AEC110EFEDA58B7235893F@excite.int.sw-soft.com>
2007-10-26 21:59 ` [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2) Eric W. Biederman
2007-10-27  0:24   ` Adrian Bunk
2007-10-27  1:31     ` Eric W. Biederman
2007-10-27  2:04       ` Adrian Bunk
2007-10-27  2:18         ` Andrew Morton
2007-10-27  3:46           ` Eric W. Biederman
2007-10-27  4:03             ` Adrian Bunk
2007-10-27  4:40               ` Eric W. Biederman
2007-10-27  5:17                 ` Adrian Bunk
2007-10-27  4:40             ` Andrew Morton
2007-10-27  7:41               ` Eric W. Biederman
2007-10-29 18:05             ` Cedric Le Goater
2007-10-29 19:11               ` Eric W. Biederman
2007-10-28 16:12       ` Jeremy Fitzhardinge
2007-10-28 17:00         ` Adrian Bunk
2007-10-28 18:31           ` Eric W. Biederman
2007-10-29 10:13             ` Cedric Le Goater [this message]
2007-10-29 18:08               ` Eric W. Biederman
2007-10-26 22:34 ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4725B256.3020807@fr.ibm.com \
    --to=clg@fr.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=jeremy@goop.org \
    --cc=kir@openvz.org \
    --cc=kir@swsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox