From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [REVIEW][PATCH 3/5] pidns: Don't have unshare(CLONE_NEWPID) imply CLONE_THREAD
Date: Fri, 30 Aug 2013 16:38:05 +0000 [thread overview]
Message-ID: <20130830163805.GB18857@mail.hallyn.com> (raw)
In-Reply-To: <87a9k0yrvu.fsf@xmission.com>
Quoting Eric W. Biederman (ebiederm@xmission.com):
>
> I goofed when I made unshare(CLONE_NEWPID) only work in a
> single-threaded process. There is no need for that requirement and in
> fact I analyzied things right for setns. The hard requirement
> is for tasks that share a VM to all be in the pid namespace and
> we properly prevent that in do_fork.
I don't understand though - copy_process does have the right test:
1176 * If the new process will be in a different pid namespace
1177 * don't allow the creation of threads.
1178 */
1179 if ((clone_flags & (CLONE_VM|CLONE_NEWPID)) &&
1180 (task_active_pid_ns(current) != current->nsproxy->pid_ns))
1181 return ERR_PTR(-EINVAL);
but why is it ok for sys_unshare not to do that? Note that
in order for check_unshare_flags() to bail on ¤t->mm->mm_users > 1
you do have to set CLONE_VM (for inverse interpretation).
So it seems to me this isn't safe as is, and we need to at least
set CLONE_VM if CLONE_PID is set.
> Just to be certain I took a look through do_wait and
> forget_original_parent and there are no cases that make it any harder
> for children to be in the multiple pid namespaces than it is for
> children to be in the same pid namespace. I also performed a check to
> see if there were in uses of task->nsproxy_pid_ns I was not familiar
> with, but it is only used when allocating a new pid for a new task,
> and in checks to prevent craziness from happening.
>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
> ---
> kernel/fork.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 66635c8..eb45f1d 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1818,11 +1818,6 @@ SYSCALL_DEFINE1(unshare, unsigned long, unshare_flags)
> if (unshare_flags & CLONE_NEWUSER)
> unshare_flags |= CLONE_THREAD | CLONE_FS;
> /*
> - * If unsharing a pid namespace must also unshare the thread.
> - */
> - if (unshare_flags & CLONE_NEWPID)
> - unshare_flags |= CLONE_THREAD;
> - /*
> * If unsharing a thread from a thread group, must also unshare vm.
> */
> if (unshare_flags & CLONE_THREAD)
> --
> 1.7.5.4
next prev parent reply other threads:[~2013-08-30 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 23:52 [REVIEW][PATCH 0/5] A couple of lingering namespace patches Eric W. Biederman
2013-08-29 23:53 ` [REVIEW][PATCH 1/5] namespaces: Simplify copy_namespaces so it is clear what is going on Eric W. Biederman
2013-08-30 16:10 ` Serge E. Hallyn
2013-08-29 23:54 ` [REVIEW][PATCH 2/5] userns: Allow PR_CAPBSET_DROP in a user namespace Eric W. Biederman
2013-08-30 1:15 ` Serge E. Hallyn
2013-08-29 23:55 ` [REVIEW][PATCH 3/5] pidns: Don't have unshare(CLONE_NEWPID) imply CLONE_THREAD Eric W. Biederman
2013-08-30 16:38 ` Serge E. Hallyn [this message]
2013-08-30 23:49 ` Eric W. Biederman
2013-08-31 5:31 ` Serge E. Hallyn
2013-09-08 17:00 ` Oleg Nesterov
2013-08-29 23:55 ` [REVIEW][PATCH 4/5] capabilities: allow nice if we are privileged Eric W. Biederman
2013-08-29 23:56 ` [REVIEW][PATCH 5/5] userns: Kill nsown_capable it makes the wrong thing easy Eric W. Biederman
2013-08-30 1:14 ` 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=20130830163805.GB18857@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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;
as well as URLs for NNTP newsgroup(s).