From: ebiederm@xmission.com (Eric W. Biederman)
To: "Kir Kolyshkin" <kir@openvz.org>
Cc: <containers@lists.osdl.org>, <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <torvalds@linux-foundation.org>
Subject: Re: [Devel] [PATCH] pidns: Place under CONFIG_EXPERIMENTAL (take 2)
Date: Fri, 26 Oct 2007 16:34:28 -0600 [thread overview]
Message-ID: <m1abq5y07f.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <CBC546DD07068244AEC110EFEDA58B7235893F@excite.int.sw-soft.com> (Kir Kolyshkin's message of "Fri, 26 Oct 2007 16:58:32 -0400")
"Kir Kolyshkin" <kir@swsoft.com> writes:
> Speaking of this particular patch -- I don't understand how you fix
> "innumerable little bugs" by providing stubs instead of real functions.
I think it would be a disaster to use pid namespaces as currently
implemented 2.6.24-rc1 in a production environment.
There are lots of little bugs and I am certain know one knows what
they are all right now.
Therefore not creating more then the initial pid namespace in a
production environment sounds like the responsible thing to do for
2.6.24.
This patch enables people to guarantee they don't run software
that will create additional pid namespaces and expose them to
the bugs we have not yet found, and it says look out. Don't
mess with this unless you know what you are doing.
That message of Look out be careful is what I really care
about sending to users of the kernel.
The best way I know to do that is to mark the feature
(EXPERIMENTAL) and have a config option for the feature
that depends on CONFIG_EXPERIMENTAL.
Eric
prev parent reply other threads:[~2007-10-26 22:35 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
2007-10-29 18:08 ` Eric W. Biederman
2007-10-26 22:34 ` Eric W. Biederman [this message]
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=m1abq5y07f.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=kir@openvz.org \
--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