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 17:39:42 +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 #44 from Torvald Riegel <triegel at redhat dot com> ---
Looking closely, the wakeup seems to come from the CLONE_CHILD_CLEARTID that
you used, which is specified as:
CLONE_CHILD_CLEARTID (since Linux 2.5.49)
Erase child thread ID at location ctid in child memory when the
child exits, and do a wakeup on the futex at that address.
Without this flag, I don't see non-spurious wakeups anymore.
--
You are receiving this mail because:
You are on the CC list for the bug.