From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13871 invoked by alias); 3 Oct 2012 05:27:29 -0000 Received: (qmail 13661 invoked by uid 48); 3 Oct 2012 05:27:09 -0000 From: "siddhesh at redhat dot com" To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14652] Cancelling a pthread_cond_wait with PRIO_INHERIT mutex causes a deadlock Date: Wed, 03 Oct 2012 05:27: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-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: siddhesh at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: siddhesh at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-10/txt/msg00018.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14652 Siddhesh Poyarekar changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Siddhesh Poyarekar 2012-10-03 05:27:08 UTC --- Thanks for documenting the problem. It is only related to this bug at a very high level though, since it applies specifically to the pthread_cond_*wait implementation on x86_64 and i386, which is fundamentally different from the cancellation points in syscall wrappers. The syscall wrappers don't have any cancellation handling on their own. pthread_cond_*wait code on the other hand already does cancellation handling with its exception tables and the condvar_cleanup function, so the fix for this specific problem is not very complicated. There is the other problem of a cancel being called on a thread that was in an async-cancel-unsafe signal handler that got called when async cancellation was enabled, but that again will have to be treated differently. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.