From: Christian Brauner <christian.brauner@ubuntu.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <christian@brauner.io>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Sargun Dhillon <sargun@sargun.me>,
Aleksa Sarai <cyphar@cyphar.com>,
linux-kselftest@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Jens Axboe <axboe@kernel.dk>,
linux-api@vger.kernel.org, Jann Horn <jannh@google.com>
Subject: Re: [PATCH 2/4] exit: support non-blocking pidfds
Date: Tue, 1 Sep 2020 18:18:40 +0200 [thread overview]
Message-ID: <20200901161840.e5eo33ctmq7zavak@wittgenstein> (raw)
In-Reply-To: <20200901161154.GA4386@redhat.com>
On Tue, Sep 01, 2020 at 06:11:54PM +0200, Oleg Nesterov wrote:
> On 08/31, Christian Brauner wrote:
> >
> > --- a/kernel/exit.c
> > +++ b/kernel/exit.c
> > @@ -934,6 +934,7 @@ struct wait_opts {
> >
> > wait_queue_entry_t child_wait;
> > int notask_error;
> > + int eagain_error;
> > };
> >
> > static int eligible_pid(struct wait_opts *wo, struct task_struct *p)
> > @@ -1461,6 +1462,8 @@ static long do_wait(struct wait_opts *wo)
> >
> > notask:
> > retval = wo->notask_error;
> > + if (!retval)
> > + retval = wo->eagain_error;
> > if (!retval && !(wo->wo_flags & WNOHANG)) {
> > retval = -ERESTARTSYS;
>
> I must have missed something but I don't understand why do we need
> the new ->eagain_error and the change in do_wait().
>
> > @@ -1544,6 +1551,11 @@ static long kernel_waitid(int which, pid_t upid, struct waitid_info *infop,
> > wo.wo_flags = options;
> > wo.wo_info = infop;
> > wo.wo_rusage = ru;
> > + wo.eagain_error = 0;
> > + if (f_flags & O_NONBLOCK) {
> > + wo.wo_flags |= WNOHANG;
> > + wo.eagain_error = -EAGAIN;
> > + }
> > ret = do_wait(&wo);
>
> Can't kernel_waitid() simply do
>
> if (f_flags & O_NONBLOCK)
> wo.wo_flags |= WNOHANG;
> ret = do_wait();
> if (!ret & (f_flags & O_NONBLOCK))
> ret = -EAGAIN;
>
> ?
Heh, indeed, that's even a smaller patch. Will change to that!
Thanks for the review, Oleg!
Christia
next prev parent reply other threads:[~2020-09-01 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 13:45 [PATCH 0/4] Support non-blocking pidfds Christian Brauner
2020-08-31 13:45 ` [PATCH 1/4] pidfd: support PIDFD_NONBLOCK in pidfd_open() Christian Brauner
2020-09-01 16:23 ` Oleg Nesterov
2020-09-01 16:33 ` Christian Brauner
2020-09-01 16:53 ` Oleg Nesterov
2020-08-31 13:45 ` [PATCH 2/4] exit: support non-blocking pidfds Christian Brauner
2020-09-01 16:11 ` Oleg Nesterov
2020-09-01 16:18 ` Christian Brauner [this message]
2020-08-31 13:45 ` [PATCH 3/4] tests: port pidfd_wait to kselftest harness Christian Brauner
2020-08-31 13:45 ` [PATCH 4/4] tests: add waitid() tests for non-blocking pidfds 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=20200901161840.e5eo33ctmq7zavak@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sargun@sargun.me \
--cc=tglx@linutronix.de \
/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