This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/417] 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:51:30 -0000
- Subject: [Bug nptl/417] pthread_mutex_timedlock can sometime consume a futex_wake signal and return a timeout -- leading to a hang.
- References: <20040930094710.417.sebastien.decugis@ext.bull.net>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From sebastien dot decugis at ext dot bull dot net 2004-09-30 09:51 -------
Created an attachment (id=212)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=212&action=view)
patch attempt to correct the bug for i486 architecture
Here is an attempt I made to correct the problem. I'm not sure if there are no
undesirable side effects. The basics is that if the futex was in "1" state, we
change it to "2". The only problem I can see is that we will eventually enter
the kernel on a mutex_unlock where it would not be necessary....
--
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.