From: ebiederm@xmission.com (Eric W. Biederman)
To: Glauber Costa <glommer@parallels.com>
Cc: Daniel Lezcano <daniel.lezcano@free.fr>,
Serge Hallyn <serge.hallyn@canonical.com>, <kir@parallels.com>,
<Michael@openvz.org>, Oleg Nesterov <oleg@redhat.com>,
<linux-kernel@vger.kernel.org>, Kerrisk <mtk.manpages@gmail.com>,
Tejun Heo <tj@kernel.org>, <cgroups@vger.kernel.org>,
<devel@openvz.org>
Subject: Re: [Devel] Re: [PATCH] allow a task to join a pid namespace
Date: Tue, 05 Jun 2012 10:39:09 -0700 [thread overview]
Message-ID: <87r4tt64le.fsf@xmission.com> (raw)
In-Reply-To: <4FCDD8A0.1070608@parallels.com> (Glauber Costa's message of "Tue, 5 Jun 2012 14:00:00 +0400")
> Eric, what are your plans for merging the content of that tree ?
Hopefully this cycle.
The issue with the pid namespace is primarily that we need to fix
all of the life cycle issues with the pid namespace and make certain
that setns adding an additional pid in a pid namespace does not break
those pid namespace life cycle fixes.
So I have been working on the hard tricky fixes off and on with Oleg.
Eric
next prev parent reply other threads:[~2012-06-05 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 13:33 [PATCH] allow a task to join a pid namespace Glauber Costa
2012-06-04 16:51 ` Oleg Nesterov
2012-06-05 9:30 ` Daniel Lezcano
2012-06-05 17:18 ` Eric W. Biederman
2012-06-05 9:36 ` Daniel Lezcano
2012-06-05 9:37 ` Glauber Costa
2012-06-05 10:00 ` [Devel] " Glauber Costa
2012-06-05 12:52 ` Daniel Lezcano
2012-06-05 12:53 ` Glauber Costa
2012-06-05 13:18 ` Daniel Lezcano
2012-06-05 17:39 ` Eric W. Biederman [this message]
2012-06-05 11:33 ` Glauber Costa
2012-06-06 18:29 ` Eric W. Biederman
2012-06-05 16:49 ` Eric W. Biederman
2012-06-06 8:54 ` Glauber Costa
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=87r4tt64le.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=Michael@openvz.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel.lezcano@free.fr \
--cc=devel@openvz.org \
--cc=glommer@parallels.com \
--cc=kir@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=serge.hallyn@canonical.com \
--cc=tj@kernel.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