From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-17567-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 2347 invoked by alias); 13 Dec 2012 20:55:48 -0000
Received: (qmail 2253 invoked by uid 48); 13 Dec 2012 20:55:26 -0000
From: "daniel.stodden at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/14958] New: Concurrent reader deadlock in pthread_rwlock_rdlock()
Date: Thu, 13 Dec 2012 20:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel.stodden at gmail 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-Changed-Fields:
Message-ID: <bug-14958-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-12/txt/msg00126.txt.bz2

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

             Bug #: 14958
           Summary: Concurrent reader deadlock in pthread_rwlock_rdlock()
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: daniel.stodden@gmail.com
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


Created attachment 6780
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6780
Example program provoking concurrent reader deadlock.

We believe we found a deadlock scenario in NPTL's rwlock implementation, 
relating to additional scheduling dependencies which NPTL imposes on 
concurrent readers.

It happens when facing sufficient congestion between both 
read- and write-locking candidates queued.

The code attached was tested on eglibc 2.15, but we believe the same
issue remains present in any more recent version of glibc and eglibc
we've seen.

It contains additional comments and a description of an event series
which lead to readers never woken, despite the rwlock being held in
read-locked mode.

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