From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH RFC] nsproxy: strengthen the comment above copy_namespaces
Date: Mon, 14 Jun 2010 22:54:13 -0400 [thread overview]
Message-ID: <4C16EB55.1090101@cs.columbia.edu> (raw)
In-Reply-To: <20100430183638.GA29240-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge -
Is this intended for linux-cr ?
Sounds like it should go (or already?) upstream.
Oren.
On 04/30/2010 02:36 PM, Serge E. Hallyn wrote:
> copy_namespaces() cannot be used on a live task. There are two
> reasons - it can be used to assign another task's nsproxy, which
> is not legal (for a live task). And, it does not use
> rcu_assign_pointer, so even when we're being extra-clever it is
> unsafe.
>
> Signed-off-by: Serge Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
> kernel/nsproxy.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/nsproxy.c b/kernel/nsproxy.c
> index f74e6c0..67d8f2b 100644
> --- a/kernel/nsproxy.c
> +++ b/kernel/nsproxy.c
> @@ -115,6 +115,9 @@ out_ns:
> /*
> * called from clone. This now handles copy for nsproxy and all
> * namespaces therein.
> + * Note this should only be used in fork. Specifically, tsk should
> + * not yet be a live task. See the the unshare code for how to handle
> + * that.
> */
> int copy_namespaces(unsigned long flags, struct task_struct *tsk)
> {
next prev parent reply other threads:[~2010-06-15 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 18:36 [PATCH RFC] nsproxy: strengthen the comment above copy_namespaces Serge E. Hallyn
[not found] ` <20100430183638.GA29240-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-06-15 2:54 ` Oren Laadan [this message]
[not found] ` <4C16EB55.1090101-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-06-15 20:37 ` 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=4C16EB55.1090101@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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 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.