From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21168 invoked by alias); 20 Jun 2014 19:02:34 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 21075 invoked by uid 55); 20 Jun 2014 19:02:30 -0000 From: "bugdal at aerifal dot cx" To: glibc-bugs@sourceware.org Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access Date: Fri, 20 Jun 2014 19:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: 2.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugdal at aerifal dot cx X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: carlos at redhat dot com X-Bugzilla-Target-Milestone: 2.18 X-Bugzilla-Flags: review? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-06/txt/msg01347.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=13690 --- Comment #39 from Rich Felker --- 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.