From: Torvald Riegel <triegel@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
"Zijlstra, Peter" <peter.zijlstra@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rich Felker <dalias@libc.org>
Subject: Re: Robust futexes: lost wakeups and design flaws in the glibc/kernel synchronization scheme
Date: Fri, 13 Jan 2017 23:25:15 +0100 [thread overview]
Message-ID: <1484346315.5606.313.camel@redhat.com> (raw)
In-Reply-To: <1484213984.5606.272.camel@redhat.com>
On Thu, 2017-01-12 at 10:39 +0100, Torvald Riegel wrote:
> On Sat, 2016-12-24 at 17:01 +0100, Torvald Riegel wrote:
> > === Robust mutexes have bugs, in both glibc and the kernel
> >
> > I've been reviewing the implementation of robust mutexes in both glibc
> > and the kernel support code recently because there are several bug
> > reports, for example:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1401665
> > https://sourceware.org/bugzilla/show_bug.cgi?id=19402
> > https://sourceware.org/bugzilla/show_bug.cgi?id=14485
> >
> > This review revealed a bunch of bugs. I have committed/proposed patches
> > that fix all glibc-only bugs that I am aware of:
> > https://sourceware.org/ml/libc-alpha/2016-12/msg00587.html
> > https://sourceware.org/ml/libc-alpha/2016-12/msg00862.html
> > https://sourceware.org/ml/libc-alpha/2016-12/msg00863.html
> > https://sourceware.org/ml/libc-alpha/2016-12/msg00947.html
These patches are now all committed to glibc master. Thus, you can
start fixing/testing now and have a high probability that you won't run
into glibc bugs.
prev parent reply other threads:[~2017-01-13 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 16:01 Robust futexes: lost wakeups and design flaws in the glibc/kernel synchronization scheme Torvald Riegel
2017-01-12 9:39 ` Torvald Riegel
2017-01-13 22:25 ` Torvald Riegel [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=1484346315.5606.313.camel@redhat.com \
--to=triegel@redhat.com \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.zijlstra@intel.com \
--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.