linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Christian Brauner <christian@brauner.io>
Cc: Anatoly Pugachev <matorola@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clone: fix CLONE_PIDFD support
Date: Sun, 14 Jul 2019 17:10:08 +0300	[thread overview]
Message-ID: <20190714141007.GA9131@altlinux.org> (raw)
In-Reply-To: <20190714121724.mwg2t3di6goha7yq@brauner.io>

[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]

On Sun, Jul 14, 2019 at 02:17:25PM +0200, Christian Brauner wrote:
> On Sun, Jul 14, 2019 at 03:02:06PM +0300, Dmitry V. Levin wrote:
> > The introduction of clone3 syscall accidentally broke CLONE_PIDFD
> > support in traditional clone syscall on compat x86 and those
> > architectures that use do_fork to implement clone syscall.
> > 
> > This bug was found by strace test suite.
> > 
> > Link: https://strace.io/logs/strace/2019-07-12
> > Fixes: 7f192e3cd316 ("fork: add clone3")
> > Bisected-and-tested-by: Anatoly Pugachev <matorola@gmail.com>
> > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> 
> Good catch! Thank you Dmitry.
> 
> One change request below.
> 
> > ---
> >  arch/x86/ia32/sys_ia32.c | 1 +
> >  kernel/fork.c            | 1 +
> >  2 files changed, 2 insertions(+)
> > 
> > diff --git a/arch/x86/ia32/sys_ia32.c b/arch/x86/ia32/sys_ia32.c
> > index 64a6c952091e..98754baf411a 100644
> > --- a/arch/x86/ia32/sys_ia32.c
> > +++ b/arch/x86/ia32/sys_ia32.c
> > @@ -239,6 +239,7 @@ COMPAT_SYSCALL_DEFINE5(x86_clone, unsigned long, clone_flags,
> >  {
> >  	struct kernel_clone_args args = {
> >  		.flags		= (clone_flags & ~CSIGNAL),
> > +		.pidfd		= parent_tidptr,
> >  		.child_tid	= child_tidptr,
> >  		.parent_tid	= parent_tidptr,
> >  		.exit_signal	= (clone_flags & CSIGNAL),
> > diff --git a/kernel/fork.c b/kernel/fork.c
> > index 8f3e2d97d771..2c3cbad807b6 100644
> > --- a/kernel/fork.c
> > +++ b/kernel/fork.c
> > @@ -2417,6 +2417,7 @@ long do_fork(unsigned long clone_flags,
> >  {
> >  	struct kernel_clone_args args = {
> >  		.flags		= (clone_flags & ~CSIGNAL),
> > +		.pidfd		= parent_tidptr,
> >  		.child_tid	= child_tidptr,
> >  		.parent_tid	= parent_tidptr,
> >  		.exit_signal	= (clone_flags & CSIGNAL),
> > -- 
> 
> Both of these legacy clone helpers need to make CLONE_PIDFD and
> CLONE_PARENT_SETTID incompatible, i.e. could you please add a helper to
> kernel/fork.c:
> 
> bool legacy_clone_args_valid(const struct kernel_clone_args *kargs)
> {
> 	/* clone(CLONE_PIDFD) uses parent_tidptr to return a pidfd */
> 	if ((kargs->flags & CLONE_PIDFD) && (kargs->flags & CLONE_PARENT_SETTID))
> 		return false;
> }
> 
> and export it and use it in ia32 too?

copy_process already performs the check, isn't this enough?
Also, the check in sys_clone looks redundant and I was going to suggest
its removal.


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2019-07-14 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 12:02 [PATCH] clone: fix CLONE_PIDFD support Dmitry V. Levin
2019-07-14 12:17 ` Christian Brauner
2019-07-14 14:10   ` Dmitry V. Levin [this message]
2019-07-14 14:23     ` Christian Brauner
2019-07-14 16:14       ` Dmitry V. Levin
2019-07-14 16:20         ` [PATCH v2] " Dmitry V. Levin
2019-07-14 18:21           ` Christian Brauner

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=20190714141007.GA9131@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=christian@brauner.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matorola@gmail.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).