From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, xemul@parallels.com
Subject: Re: [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parent pidns
Date: Fri, 8 May 2009 14:15:52 -0500 [thread overview]
Message-ID: <20090508191552.GA28885@us.ibm.com> (raw)
In-Reply-To: <20090503232700.GD16631@x200.localdomain>
Quoting Alexey Dobriyan (adobriyan@gmail.com):
> create_pid_namespace() creates everything, but caller has to assign parent
> pidns by hand, which is unnatural. At the moment of call new ->level has
> to be taken from somewhere and parent pidns is already available.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Yes, nicer.
Acked-by: Serge Hallyn <serue@us.ibm.com>
> ---
> kernel/pid_namespace.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
> index 2d1001b..495d5de 100644
> --- a/kernel/pid_namespace.c
> +++ b/kernel/pid_namespace.c
> @@ -67,9 +67,10 @@ err_alloc:
> return NULL;
> }
>
> -static struct pid_namespace *create_pid_namespace(unsigned int level)
> +static struct pid_namespace *create_pid_namespace(struct pid_namespace *parent_pid_ns)
> {
> struct pid_namespace *ns;
> + unsigned int level = parent_pid_ns->level + 1;
> int i;
>
> ns = kmem_cache_zalloc(pid_ns_cachep, GFP_KERNEL);
> @@ -86,6 +87,7 @@ static struct pid_namespace *create_pid_namespace(unsigned int level)
>
> kref_init(&ns->kref);
> ns->level = level;
> + ns->parent = get_pid_ns(parent_pid_ns);
>
> set_bit(0, ns->pidmap[0].page);
> atomic_set(&ns->pidmap[0].nr_free, BITS_PER_PAGE - 1);
> @@ -125,9 +127,7 @@ struct pid_namespace *copy_pid_ns(unsigned long flags, struct pid_namespace *old
> if (flags & CLONE_THREAD)
> goto out_put;
>
> - new_ns = create_pid_namespace(old_ns->level + 1);
> - if (!IS_ERR(new_ns))
> - new_ns->parent = get_pid_ns(old_ns);
> + new_ns = create_pid_namespace(old_ns);
>
> out_put:
> put_pid_ns(old_ns);
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2009-05-08 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 23:27 [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parent pidns Alexey Dobriyan
[not found] ` <20090503232700.GD16631-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2009-05-05 1:58 ` [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parentpidns Sukadev Bhattiprolu
2009-05-08 19:15 ` [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parent pidns Serge E. Hallyn
2009-05-05 1:58 ` [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parentpidns Sukadev Bhattiprolu
2009-05-08 19:15 ` Serge E. Hallyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-03 23:27 [PATCH 1/2] pidns 1/2: make create_pid_namespace() accept parent pidns Alexey Dobriyan
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=20090508191552.GA28885@us.ibm.com \
--to=serue@us.ibm.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.