From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
Subject: Re: RT trees fail ltp futex_wait04 - culprit=65d8fc777f6d (futex: Remove requirement for lock_page() in get_futex_key())
Date: Thu, 9 Jun 2016 14:04:00 +0200 [thread overview]
Message-ID: <20160609120400.GA6305@linutronix.de> (raw)
In-Reply-To: <1465057019.4178.0.camel@gmail.com>
- Mel, tglx
* Mike Galbraith | 2016-06-04 18:16:59 [+0200]:
>On Sat, 2016-06-04 at 18:07 +0200, Mike Galbraith wrote:
>> Oho, actually, it's not only RT kernels, master with an enterprise like
>> NOPREEMPT config fails as well, so it's a garden variety regression.
>>
>> futex_wake04 1 TFAIL : futex_wake04.c:126: Bug: wait_thread2 did not wake after 30 secs.
>
>And again, swiped bits fixed it.
for reference, this thread ends here:
http://git.kernel.org/tip/077fa7aed17de5022e44bf07dbaf732078b7b5b2
Sebastian
prev parent reply other threads:[~2016-06-09 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 14:53 RT trees fail ltp futex_wait04 - culprit=65d8fc777f6d (futex: Remove requirement for lock_page() in get_futex_key()) Mike Galbraith
2016-06-04 16:07 ` Mike Galbraith
2016-06-04 16:16 ` Mike Galbraith
2016-06-09 12:04 ` Sebastian Andrzej Siewior [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=20160609120400.GA6305@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=umgwanakikbuti@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).