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 2/2] pidns 2/2: rewrite copy_pid_ns()
Date: Fri, 8 May 2009 14:19:22 -0500 [thread overview]
Message-ID: <20090508191922.GB28885@us.ibm.com> (raw)
In-Reply-To: <20090503232721.GE16631@x200.localdomain>
Quoting Alexey Dobriyan (adobriyan@gmail.com):
> copy_pid_ns() is a perfect example of a case where unwinding leads to more
> code and makes it less clear. Watch the diffstat.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Nice.
Reviewed-by: Serge Hallyn <serue@us.ibm.com>
thanks,
-serge
> ---
> kernel/pid_namespace.c | 18 +++---------------
> 1 files changed, 3 insertions(+), 15 deletions(-)
>
> diff --git a/kernel/pid_namespace.c b/kernel/pid_namespace.c
> index 495d5de..821722a 100644
> --- a/kernel/pid_namespace.c
> +++ b/kernel/pid_namespace.c
> @@ -116,23 +116,11 @@ static void destroy_pid_namespace(struct pid_namespace *ns)
>
> struct pid_namespace *copy_pid_ns(unsigned long flags, struct pid_namespace *old_ns)
> {
> - struct pid_namespace *new_ns;
> -
> - BUG_ON(!old_ns);
> - new_ns = get_pid_ns(old_ns);
> if (!(flags & CLONE_NEWPID))
> - goto out;
> -
> - new_ns = ERR_PTR(-EINVAL);
> + return get_pid_ns(old_ns);
> if (flags & CLONE_THREAD)
> - goto out_put;
> -
> - new_ns = create_pid_namespace(old_ns);
> -
> -out_put:
> - put_pid_ns(old_ns);
> -out:
> - return new_ns;
> + return ERR_PTR(-EINVAL);
> + return create_pid_namespace(old_ns);
> }
>
> void free_pid_ns(struct kref *kref)
> _______________________________________________
> 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:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 23:27 [PATCH 2/2] pidns 2/2: rewrite copy_pid_ns() Alexey Dobriyan
2009-05-03 23:27 ` Alexey Dobriyan
2009-05-05 1:59 ` Sukadev Bhattiprolu
2009-05-08 19:19 ` Serge E. Hallyn [this message]
[not found] ` <20090503232721.GE16631-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2009-05-05 1:59 ` Sukadev Bhattiprolu
2009-05-08 19:19 ` Serge E. Hallyn
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=20090508191922.GB28885@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.