From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25483 invoked by alias); 6 Mar 2014 16:03:48 -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 25400 invoked by uid 48); 6 Mar 2014 16:03:40 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/16657] Lock elision breaks pthread_mutex_detroy Date: Thu, 06 Mar 2014 16:03: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.18 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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-03/txt/msg00034.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16657 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #7 from Carlos O'Donell --- (In reply to Rich Felker from comment #6) > It's certainly not "undefined", It's required to return 0 on success, and > there are no defined errors for destroy in POSIX, so any error returned > would need to be implementation-defined or occur only in the case of > undefined behavior. I agree. With elision you can't detect the EINVAL or EBUSY cases, therefore returning 0 when elision is enabled is the best solution. What do you think Andi? -- You are receiving this mail because: You are on the CC list for the bug.