From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: commit 67d7ddded32 (waitid(2): leave copyout of siginfo to syscall itself) breaks glibc posix/tst-waitid
Date: Sat, 8 Jul 2017 15:53:16 +0200 [thread overview]
Message-ID: <20170708135316.GA277@x4> (raw)
In-Reply-To: <20170708131218.GP10672@ZenIV.linux.org.uk>
On 2017.07.08 at 14:12 +0100, Al Viro wrote:
> On Sat, Jul 08, 2017 at 11:56:44AM +0200, Markus Trippelsdorf wrote:
> > Since:
> > commit 67d7ddded322db99f451a7959d56ed6c70a6c4aa
> > Author: Al Viro <viro@zeniv.linux.org.uk>
> > Date: Sun May 14 20:53:13 2017 -0400
> >
> > waitid(2): leave copyout of siginfo to syscall itself
> >
> > the glibc posix/tst-waitid.c testcase fails:
> >
> > markus@x4 glibc-build % ./posix/tst-waitid
> > waitid WNOHANG on stopped status 0
>
> I think I see what's going on... We lose the distinction between "got
> a PID" and "nothing, but that's not an error" a bit too early waitid()
> case. Could you see if there are any problems left with the following
> applied?
No, everything looks nice now. Thanks.
--
Markus
prev parent reply other threads:[~2017-07-08 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 9:56 commit 67d7ddded32 (waitid(2): leave copyout of siginfo to syscall itself) breaks glibc posix/tst-waitid Markus Trippelsdorf
2017-07-08 13:12 ` Al Viro
2017-07-08 13:53 ` Markus Trippelsdorf [this message]
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=20170708135316.GA277@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.