This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/21390] robust pthread_mutex_t deadlock from 2.24 -> 2.25
- From: "triegel at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 18 Apr 2017 19:55:49 +0000
- Subject: [Bug nptl/21390] robust pthread_mutex_t deadlock from 2.24 -> 2.25
- Auto-submitted: auto-generated
- References: <bug-21390-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21390
--- Comment #1 from Torvald Riegel <triegel at redhat dot com> ---
I think we need a reproducer. The stackoverflow problem description is
incomplete and it mentions that this is timing-dependent (eg, adding logging to
the application seems to prevent the problem); however, the description of the
problem makes it sounds as if just a deterministic access by more than one
thread by the same process would cause the problem to appear (which seems
unlikely).
There were changes in the robust mutex code in the 2.25 release, but all those
were fixing bugs in the robust mutexes. We could have introduced other errors
when doing that, or the code simply runs into the robust mutex bugs that are
still present in the kernel. Without a reproducer, we can't investigate this
further.
--
You are receiving this mail because:
You are on the CC list for the bug.