public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/13184] rwlocks can go into dead lock
Date: Fri, 13 Jun 2014 14:29:00 -0000 [thread overview]
Message-ID: <bug-13184-131-pkl1V7gzVR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13184-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13184
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fweimer at redhat dot com
Resolution|--- |WONTFIX
Flags| |security-
--- Comment #13 from Florian Weimer <fweimer at redhat dot com> ---
I don't think we can fix such hardware errata, certainly not without support
from the CPU vendor.
In this particular case, the affected CPU was released in 2005, so it is not
very likely this part is available anymore.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-13 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 21:19 [Bug nptl/13184] New: " redhat at pureftpd dot org
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 [this message]
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-pkl1V7gzVR@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).