From: Christian Brauner <christian@brauner.io>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, oleg@redhat.com,
torvalds@linux-foundation.org, arnd@arndb.de,
ebiederm@xmission.com, joel@joelfernandes.org,
tglx@linutronix.de, tj@kernel.org, dhowells@redhat.com,
jannh@google.com, luto@kernel.org, akpm@linux-foundation.org,
cyphar@cyphar.com, viro@zeniv.linux.org.uk,
kernel-team@android.com
Subject: Re: [PATCH v3 1/2] pidfd: add P_PIDFD to waitid()
Date: Mon, 29 Jul 2019 19:56:21 +0200 [thread overview]
Message-ID: <20190729175620.uwszsvidnb2cmul4@brauner.io> (raw)
In-Reply-To: <201907290915.8B421306D@keescook>
On Mon, Jul 29, 2019 at 09:24:38AM -0700, Kees Cook wrote:
> On Sun, Jul 28, 2019 at 12:22:29AM +0200, Christian Brauner wrote:
> > diff --git a/kernel/exit.c b/kernel/exit.c
> > index a75b6a7f458a..64bb6893a37d 100644
> > --- a/kernel/exit.c
> > +++ b/kernel/exit.c
> > @@ -1552,6 +1552,23 @@ static long do_wait(struct wait_opts *wo)
> > return retval;
> > }
> >
> > +static struct pid *pidfd_get_pid(unsigned int fd)
> > +{
> > + struct fd f;
> > + struct pid *pid;
> > +
> > + f = fdget(fd);
> > + if (!f.file)
> > + return ERR_PTR(-EBADF);
> > +
> > + pid = pidfd_pid(f.file);
> > + if (!IS_ERR(pid))
> > + get_pid(pid);
> > +
> > + fdput(f);
> > + return pid;
> > +}
> > +
> > static long kernel_waitid(int which, pid_t upid, struct waitid_info *infop,
> > int options, struct rusage *ru)
> > {
> > @@ -1574,19 +1591,29 @@ static long kernel_waitid(int which, pid_t upid, struct waitid_info *infop,
> > type = PIDTYPE_PID;
> > if (upid <= 0)
> > return -EINVAL;
> > +
> > + pid = find_get_pid(upid);
> > break;
> > case P_PGID:
> > type = PIDTYPE_PGID;
> > if (upid <= 0)
> > return -EINVAL;
> > +
> > + pid = find_get_pid(upid);
> > + break;
> > + case P_PIDFD:
> > + type = PIDTYPE_PID;
> > + if (upid < 0)
> > + return -EINVAL;
> > +
> > + pid = pidfd_get_pid(upid);
> > + if (IS_ERR(pid))
> > + return PTR_ERR(pid);
>
> I spent some time convincing myself that this early bail out was
> correct. It seems this path is only reachable in the EBADF case, so that
> makes sense. The other failure modes in this switch all give a NULL pid
> so that the final do_wait() returns ECHILD. So, as long as that's
> intentional (which I think it is), this all looks fine. :)
Yep, it is. I didn't want to refactor that out of do_wait(). :)
Thanks!
Christian
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
next prev parent reply other threads:[~2019-07-29 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 22:22 [PATCH v3 0/2] pidfd: waiting on processes through pidfds Christian Brauner
2019-07-27 22:22 ` [PATCH v3 1/2] pidfd: add P_PIDFD to waitid() Christian Brauner
2019-07-29 14:27 ` Oleg Nesterov
2019-07-29 14:54 ` Christian Brauner
2019-07-29 16:24 ` Kees Cook
2019-07-29 17:56 ` Christian Brauner [this message]
2019-07-27 22:22 ` [PATCH v3 2/2] pidfd: add pidfd_wait tests Christian Brauner
2019-07-29 16:31 ` Kees Cook
2019-07-29 17:55 ` 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=20190729175620.uwszsvidnb2cmul4@brauner.io \
--to=christian@brauner.io \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®