public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redhat at pureftpd dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/13184] New: rwlocks can go into dead lock
Date: Mon, 12 Sep 2011 21:19:00 -0000 [thread overview]
Message-ID: <bug-13184-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13184
Bug #: 13184
Summary: rwlocks can go into dead lock
Product: glibc
Version: 2.14
Status: NEW
Severity: critical
Priority: P2
Component: nptl
AssignedTo: drepper.fsp@gmail.com
ReportedBy: redhat@pureftpd.org
Classification: Unclassified
This issue can be reliably reproduced on glibc 2.7, glibc 2.11, glibc 1.14 and
glibc-current (stock, without any vendor patches).
A race condition can cause a pthreads rwlock to get a negative number of
__nr_readers, thus leading to a dead lock.
This issue seems to be hardware dependent. I haven't been able to reproduce it
on single-core Opterons nor Intel hardware. But it happens in minutes on
different boxes, all powered by dual-core Opteron 270.
A test program triggering this issue can be found at:
http://download.pureftpd.org/misc/nptl-bugs/crazylock.c
--
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.
next reply other threads:[~2011-09-12 21:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 21:19 redhat at pureftpd dot org [this message]
2011-09-12 21:33 ` [Bug nptl/13184] " bugdal at aerifal dot cx
2011-09-12 21:42 ` redhat at pureftpd dot org
2011-09-12 22:26 ` bugdal at aerifal dot cx
2011-09-12 22:41 ` redhat at pureftpd dot org
2011-09-13 1:57 ` redhat at pureftpd dot org
2011-09-13 2:02 ` redhat at pureftpd dot org
2012-01-16 20:03 ` ph.mathieu at gmail dot com
2012-01-16 21:47 ` redhat at pureftpd dot org
2012-01-17 14:54 ` ph.mathieu at gmail dot com
2012-10-04 12:31 ` siddhesh at redhat dot com
2012-10-04 12:37 ` bugdal at aerifal dot cx
2012-10-04 13:13 ` siddhesh at redhat dot com
2012-10-04 17:56 ` bugdal at aerifal dot cx
2012-10-04 17:56 ` bugdal at aerifal dot cx
2012-12-19 10:44 ` schwab@linux-m68k.org
2014-06-13 14:29 ` fweimer at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13184-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).