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 sourceware dot org
- Date: Fri, 20 Jun 2014 19:02:27 +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 #39 from Rich Felker <bugdal at aerifal dot cx> ---
On Fri, Jun 20, 2014 at 06:28:59PM +0000, triegel at redhat dot com wrote:
> The fact that the futex_wake call can now hit reused memory (i.e., after
> destruction of the mutex) is the trickier issue IMO. More details on the
> latter can be found in an email I sent a while ago to libc-alpha.
I'm not convinced that the resulting spurious futex wakes are a
serious problem. As I've mentioned before, I have observed spurious
futex wakes coming from the kernel, so applications need to be
prepared to deal with them anyway. I'll see if I can dig up and post
my test case demonstrating them.
--
You are receiving this mail because:
You are on the CC list for the bug.