From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3581 invoked by alias); 6 Jan 2014 20:47:29 -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 3500 invoked by uid 48); 6 Jan 2014 20:47:26 -0000 From: "bugdal at aerifal dot cx" To: glibc-bugs@sourceware.org Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access Date: Mon, 06 Jan 2014 20:47: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-01/txt/msg00076.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=13690 --- Comment #34 from Rich Felker --- > > or (b) wait for all threads to exit. > > Precisely, wait for all threads that use the particular resource to not use it > anymore. That's different from "wait[ing] for all threads to exit". That requires a mutex. So you just moved the mutex issue to a different mutex; you didn't solve it. > > You are arguing for (b): To destroy a mutex -- any mutex -- you must first > > wait for every thread that ever touched that mutex to exit. > > This could be a reasonable semantics. No, you stopped being reasonable several posts back in this thread. I'm not sure what your emotional attachment to glibc's current brokenness with respect to this issue is, but it's completely clouding your judgement and making you look like a fool. It's really sad to see this kind of response to bugs again when glibc was just recovering from the madness of the former maintainer and his attitude towards bug reports... -- You are receiving this mail because: You are on the CC list for the bug.