From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2185 invoked by alias); 9 Aug 2014 20:38:32 -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 2095 invoked by uid 48); 9 Aug 2014 20:38:29 -0000 From: "triegel at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access Date: Sat, 09 Aug 2014 20:38: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: triegel at redhat dot com 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-08/txt/msg00016.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=13690 --- Comment #47 from Torvald Riegel --- This would increase the unlock latency whenever there is any waiter (because we let the kernel do it, and after it has found and acquired the futex lock). I don't have numbers for this increase, but if there's a non-neglible increase in latency, then I wouldn't want to see this in glibc. I still think that the only thing we need to fix is to make sure that no program can interpret a spurious wake-up (by a pending futex_wake) as a real wake-up. -- You are receiving this mail because: You are on the CC list for the bug.