This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access
- From: "triegel at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 25 Jun 2014 14:34:13 +0000
- Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access
- Auto-submitted: auto-generated
- References: <bug-13690-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13690
--- Comment #42 from Torvald Riegel <triegel at redhat dot com> ---
Rich, thanks for the test case, but the code doesn't checks what the futex
syscall returns. The issue I'm concerned about is not whether there are
spurious wake-ups, but that a spurious wake-up can incorrectly appear to be a
non-spurious one due to the return value of the futex syscall reporting
success.
--
You are receiving this mail because:
You are on the CC list for the bug.