From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-14124-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 8267 invoked by alias); 17 Feb 2012 16:18:21 -0000
Received: (qmail 8256 invoked by uid 22791); 17 Feb 2012 16:18:20 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO sourceware.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Feb 2012 16:18:09 +0000
From: "carlos at systemhalted dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access
Date: Fri, 17 Feb 2012 16:18: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: glibc_2.15
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at systemhalted dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: carlos at systemhalted dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-13690-131-AC3BHPJE0X@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-13690-131@http.sourceware.org/bugzilla/>
References: <bug-13690-131@http.sourceware.org/bugzilla/>
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: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2012-02/txt/msg00163.txt.bz2

http://sourceware.org/bugzilla/show_bug.cgi?id=13690

--- Comment #13 from Carlos O'Donell <carlos at systemhalted dot org> 2012-02-17 16:17:25 UTC ---
(In reply to comment #11)
> If that's acceptable, you could just make the test case either a gdb script or
> a dedicated ptrace-using parent process that puts a breakpoint at the right
> location to hit the race...

I like the idea of a ptrace-using parent process to trigger the race condition,
but it's fragile. I like your suggestion though.

-- 
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.