From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Florian Weimer <fweimer@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Darren Hart <dvhart@infradead.org>
Subject: Re: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure
Date: Fri, 19 May 2017 19:35:54 +0200 [thread overview]
Message-ID: <20170519173554.GA284@x4> (raw)
In-Reply-To: <20170519154850.mlomgdsd26drq5j6@hirez.programming.kicks-ass.net>
On 2017.05.19 at 17:48 +0200, Peter Zijlstra wrote:
> On Thu, May 18, 2017 at 10:34:34AM +0200, Florian Weimer wrote:
> > On 05/18/2017 10:31 AM, Peter Zijlstra wrote:
>
> > > But it does that after building the tst-robustpi8 thing, so I seem to
> > > have all I need here.
> >
> > Great, have fun figuring out what's going on. :-/
>
> Please test the below, it cures things for me.
Thanks. The glibc testsuite now finishes without any failure.
--
Markus
next prev parent reply other threads:[~2017-05-19 17:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:36 commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure Markus Trippelsdorf
2017-05-17 17:50 ` Florian Weimer
2017-05-18 6:46 ` Peter Zijlstra
2017-05-18 6:57 ` Peter Zijlstra
2017-05-18 7:40 ` Peter Zijlstra
2017-05-18 8:04 ` Markus Trippelsdorf
2017-05-18 8:14 ` Peter Zijlstra
2017-05-18 8:12 ` Florian Weimer
2017-05-18 8:31 ` Peter Zijlstra
2017-05-18 8:34 ` Florian Weimer
2017-05-18 8:41 ` Peter Zijlstra
2017-05-18 8:42 ` Florian Weimer
2017-05-18 11:43 ` Peter Zijlstra
2017-05-18 12:30 ` Peter Zijlstra
2017-05-19 15:48 ` Peter Zijlstra
2017-05-19 16:07 ` Peter Zijlstra
2017-05-19 17:35 ` Markus Trippelsdorf [this message]
2017-05-22 20:04 ` [tip:locking/urgent] futex,rt_mutex: Fix rt_mutex_cleanup_proxy_lock() tip-bot for Peter Zijlstra
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=20170519173554.GA284@x4 \
--to=markus@trippelsdorf.de \
--cc=bigeasy@linutronix.de \
--cc=dvhart@infradead.org \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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 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.