From: Carlos O'Donell <carlos@redhat.com>
To: Stefan Liebler <stli@linux.vnet.ibm.com>, libc-alpha@sourceware.org
Subject: Re: FAIL nptl/tst-robustpi4
Date: Thu, 26 Jan 2017 16:12:00 -0000 [thread overview]
Message-ID: <ec3d5947-a1a6-a4ee-e8cd-0a47e6408cd6@redhat.com> (raw)
In-Reply-To: <b71bec8d-ef71-1903-c7a8-fafa2fa744f5@linux.vnet.ibm.com>
On 01/26/2017 10:29 AM, Stefan Liebler wrote:
> It seems as a race between futex- and exit-syscall causes ESRCH
> result from futex-syscall.
>
> I see those fails with Linux 4.8 / 4.9 running in a z/VM guest as
> well as with 4.6 on a LPAR (but less often).
I've seen tst-robustpi7 and tst-robustpi8 failures on all hardware
across a wide number of kernels, but never tst-robustpi4.
https://sourceware.org/bugzilla/show_bug.cgi?id=19004
The robustpi support is certainly not very robust as Torvald's
recent fixes show, and there still remains at least one design
flaw that can't be fixed.
e.g.
https://sourceware.org/bugzilla/show_bug.cgi?id=14485
and...
https://sourceware.org/bugzilla/show_bug.cgi?id=19089
--
Cheers,
Carlos.
next prev parent reply other threads:[~2017-01-26 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 15:29 Stefan Liebler
2017-01-26 16:12 ` Carlos O'Donell [this message]
2017-01-26 16:22 ` Torvald Riegel
2018-06-29 6:55 ` FAIL nptl/tst-robustpi4 [BZ 23183] Stefan Liebler
2018-06-29 7:39 ` Florian Weimer
2018-06-29 8:22 ` Stefan Liebler
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=ec3d5947-a1a6-a4ee-e8cd-0a47e6408cd6@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.vnet.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).