From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: akpm@linux-foundation.org, containers@lists.linux-foundation.org,
xemul@parallels.com, dave@linux.vnet.ibm.com, mingo@elte.hu,
orenl@cs.columbia.edu, hch@infradead.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/30] cr: core stuff
Date: Tue, 14 Apr 2009 21:00:04 +0400 [thread overview]
Message-ID: <20090414170004.GC27923@x200.localdomain> (raw)
In-Reply-To: <20090414154139.GA8085@us.ibm.com>
On Tue, Apr 14, 2009 at 10:41:39AM -0500, Serge E. Hallyn wrote:
> Quoting Alexey Dobriyan (adobriyan@gmail.com):
> > On Mon, Apr 13, 2009 at 04:47:01PM -0500, Serge E. Hallyn wrote:
> > > Quoting Alexey Dobriyan (adobriyan@gmail.com):
> > >
> > > Hi Alexey,
> > >
> > > as far as I can see, the main differences between this patch and the
> > > equivalent in Oren's tree are:
> > >
> > > 1. kernel auto-selects container init to freeze
> >
> > Note, auto-select part was dropped, userspace is required to pass pid of
> > container init exactly. This was done to keep semantic of checkpoint(2)
> > small and extendable.
>
> sys_checkpoint() in this patch still finds the child_reaper of the
> passed-in pid, doesn't it? Or are you saying that a later patch in
> this set removes that?
I posted with auto-selecting?
Code now looks like this:
rcu_read_lock();
tsk = find_task_by_vpid(pid);
if (tsk) {
struct nsproxy *nsproxy;
nsproxy = task_nsproxy(tsk);
if (nsproxy) {
init_tsk = nsproxy->pid_ns->child_reaper;
if (init_tsk != tsk)
init_tsk = NULL;
} else
init_tsk = NULL;
if (init_tsk)
get_task_struct(init_tsk);
}
rcu_read_unlock();
This is to buy as little semantics on checkpoint(2) as possible.
If users later will complain that it's for some reason hard to see who is
root of container, it could be added.
next prev parent reply other threads:[~2009-04-14 17:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 2:35 Alexey Dobriyan
2009-04-10 9:35 ` Ingo Molnar
2009-04-10 11:43 ` Alexey Dobriyan
2009-04-10 16:19 ` Brian Haley
2009-04-13 8:10 ` Alexey Dobriyan
2009-04-13 21:47 ` Serge E. Hallyn
2009-04-14 5:52 ` Oren Laadan
2009-04-14 15:29 ` Serge E. Hallyn
2009-04-14 16:37 ` "partial" container checkpoint Dave Hansen
2009-04-14 17:30 ` Kevin Fox
2009-04-15 0:06 ` Paul Menage
2009-04-14 15:27 ` [PATCH 10/30] cr: core stuff Alexey Dobriyan
2009-04-14 15:41 ` Dave Hansen
2009-04-14 16:57 ` Alexey Dobriyan
2009-04-14 15:41 ` Serge E. Hallyn
2009-04-14 16:48 ` Dave Hansen
2009-04-14 17:00 ` Alexey Dobriyan [this message]
2009-04-14 17:04 ` Alexey Dobriyan
2009-04-14 17:23 ` checkpoint/restart: taking refcounts on kernel objects Dave Hansen
2009-05-01 12:56 ` Alexey Dobriyan
2009-04-14 17:43 ` [PATCH 10/30] cr: core stuff Oren Laadan
2009-04-14 5:22 ` Oren Laadan
2009-04-14 16:00 ` Alexey Dobriyan
2009-04-14 16:39 ` Dave Hansen
2009-04-14 17:28 ` Alexey Dobriyan
2009-04-14 18:19 ` Oren Laadan
2009-04-14 19:00 ` Alexey Dobriyan
2009-04-14 19:26 ` 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=20090414170004.GC27923@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=serue@us.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=xemul@parallels.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®