From: Matt Helsley <matthltc@us.ibm.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Louis Rilling <Louis.Rilling@kerlabs.com>,
Linux Containers <containers@lists.osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH linux-cr] nested pid namespaces (v2)
Date: Mon, 22 Mar 2010 12:57:35 -0700 [thread overview]
Message-ID: <20100322195735.GE20796@count0.beaverton.ibm.com> (raw)
In-Reply-To: <20100322143800.GD3744@us.ibm.com>
On Mon, Mar 22, 2010 at 09:38:00AM -0500, Serge E. Hallyn wrote:
> Quoting Louis Rilling (Louis.Rilling@kerlabs.com):
> > On Fri, Mar 19, 2010 at 04:39:55PM -0500, Serge E. Hallyn wrote:
> > > Support checkpoint and restart of tasks in nested pid namespaces. At
<snip>
> > It would probably be safer too to use task_active_pid_ns() instead of
> > task->nsproxy->pid_ns, just in case some PID namespace unsharing like proposed
> > by Eric makes it to mainline.
>
> The task is frozen though so it shouldn't be able to unshare while being
> checkpointed, right? But it's probably better code anyway.
By the time it reaches checkpoint a frozen task is in the refrigerator
-- most often in the signal delivery portion of syscall return. So it can't
be making any new unshare/setns syscalls and any changes to the namespaces
should be visible.
Cheers,
-Matt Helsley
next prev parent reply other threads:[~2010-03-22 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 21:39 Serge E. Hallyn
2010-03-19 21:41 ` [PATCH] user-ns: Nested pidns support (v2) Serge E. Hallyn
2010-03-22 10:55 ` [PATCH linux-cr] nested pid namespaces (v2) Louis Rilling
2010-03-22 14:38 ` Serge E. Hallyn
2010-03-22 19:57 ` Matt Helsley [this message]
2010-03-23 6:41 ` Louis Rilling
2010-03-22 23:17 ` Oren Laadan
2010-03-23 4:26 ` Serge E. Hallyn
2010-03-23 5:39 ` Oren Laadan
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=20100322195735.GE20796@count0.beaverton.ibm.com \
--to=matthltc@us.ibm.com \
--cc=Louis.Rilling@kerlabs.com \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
/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
all inboxes | Powered by JetHome®