This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/417] New: pthread_mutex_timedlock can sometime consume a futex_wake signal and return a timeout -- leading to a hang.
- From: "sebastien dot decugis at ext dot bull dot net" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 30 Sep 2004 09:47:15 -0000
- Subject: [Bug nptl/417] New: pthread_mutex_timedlock can sometime consume a futex_wake signal and return a timeout -- leading to a hang.
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
In some circumstances, the pthread_mutex_timedlock operation can be awaken by a
call to pthread_mutex_unlock, but the timeout expires before it is scheduled. In
case the futex status is 1 when the awaken thread resumes, it will return the
timeout status and leave the futex in "1" state. In case another thread whould
be waiting for the same mutex, it will never be awaken.
This bug was first posted on 10/2003 in comp.programming.threads
http://groups.google.com/groups?selm=x74qxsrde4.fsf%40bolo.xenadyne.com
I've checked, the faulty behavior is still present in the current nptl code.
--
Summary: pthread_mutex_timedlock can sometime consume a
futex_wake signal and return a timeout -- leading to a
hang.
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: sebastien dot decugis at ext dot bull dot net
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=417
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.