mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Brad Spengler <spender@grsecurity.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Colin Walters <walters@redhat.com>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH? fix unshare(NEWPID) && vfork()
Date: Tue, 20 Aug 2013 10:55:40 -0700	[thread overview]
Message-ID: <87siy4z1pf.fsf@xmission.com> (raw)
In-Reply-To: <20130819184355.GA25362@redhat.com> (Oleg Nesterov's message of "Mon, 19 Aug 2013 20:43:55 +0200")

Oleg Nesterov <oleg@redhat.com> writes:

> On 08/19, Andy Lutomirski wrote:
>>
>> On Mon, Aug 19, 2013 at 11:33 AM, Oleg Nesterov <oleg@redhat.com> wrote:
>> >
>> > So do you think this change is fine or not (ignoring the fact it needs
>> > cleanups) ?
>>
>> I think that removing the CLONE_VM check is fine (although there are
>> some other ones that should probably be removed as well), but I'm not
>> sure if that check needs replacing with something else.
>
> OK, thanks... but I still can't understand.
>
> The patch I sent is equivalent to the new one below. I just tried to
> unify it with another check in do_fork().

The patch below also needs CLONE_SIGHAND.  You can't meaningfully share
signal handlers if you can't represent the pid in the siginfo.  pids and
signals are too interconnected.

Eric

> Oleg.
>
> --- x/kernel/fork.c
> +++ x/kernel/fork.c
> @@ -1176,7 +1176,7 @@ static struct task_struct *copy_process(
>  	 * If the new process will be in a different pid namespace
>  	 * don't allow the creation of threads.
>  	 */
> -	if ((clone_flags & (CLONE_VM|CLONE_NEWPID)) &&
> +	if ((clone_flags & (CLONE_THREAD | CLONE_PARENT | CLONE_NEWPID)) &&
>  	    (task_active_pid_ns(current) != current->nsproxy->pid_ns))
>  		return ERR_PTR(-EINVAL);
>  

  reply	other threads:[~2013-08-20 17:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 17:25 Oleg Nesterov
2013-08-19 17:46 ` Linus Torvalds
2013-08-19 17:51   ` Oleg Nesterov
2013-08-19 18:10 ` Andy Lutomirski
2013-08-19 18:33   ` Oleg Nesterov
2013-08-19 18:40     ` Andy Lutomirski
2013-08-19 18:43       ` Oleg Nesterov
2013-08-20 17:55         ` Eric W. Biederman [this message]
2013-08-20 18:45           ` Oleg Nesterov
2013-08-20 20:52             ` Eric W. Biederman
2013-08-21 16:35               ` Oleg Nesterov
2013-08-22 16:47                 ` Oleg Nesterov
2013-08-20 17:59         ` Andy Lutomirski
2013-08-20 18:50           ` Oleg Nesterov
2013-08-20 19:00             ` Andy Lutomirski
2013-08-20 19:05               ` Oleg Nesterov
2013-08-20 19:13                 ` Andy Lutomirski
2013-08-20 19:23                   ` Oleg Nesterov
2013-08-20 19:38                     ` Andy Lutomirski
2013-08-21 12:24                       ` Oleg Nesterov
2013-08-20 20:25               ` Eric W. Biederman

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=87siy4z1pf.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=oleg@redhat.com \
    --cc=spender@grsecurity.net \
    --cc=torvalds@linux-foundation.org \
    --cc=walters@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

Powered by JetHome