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: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 16 Feb 2012 05:07:32 +0000
- Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access
- Auto-submitted: auto-generated
- References: <bug-13690-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13690
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #4 from Rich Felker <bugdal at aerifal dot cx> 2012-02-16 05:07:32 UTC ---
Analogous bugs are ENDEMIC in glibc/NPTL and so far there's been a complete
unwillingless to fix them or even acknowledge that they exist. See
http://sourceware.org/bugzilla/show_bug.cgi?id=12674
Fixing the issue to ensure that a synchronization object's memory is not
touched whatsoever after it's unlocked/posted is non-trivial, but once you
figure out the solution, it's rather general-purpose. A while back I audited
all my synchronization primitives in musl libc for similar bugs and fixed them,
so it might be a useful source for ideas to fix glibc/NPTL.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.