public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/13184] rwlocks can go into dead lock Date: Thu, 04 Oct 2012 12:31:00 -0000 [thread overview] Message-ID: <bug-13184-131-QN199FkChE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13184-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13184 Siddhesh Poyarekar <siddhesh at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |siddhesh at redhat dot com --- Comment #8 from Siddhesh Poyarekar <siddhesh at redhat dot com> 2012-10-04 12:31:31 UTC --- I don't have an Opteron 270 to test this on, but it looks like something that shouldn't happen, since the instruction you've 'locked' with your patch should already be isolated with lock.__data.__lock. If the patch actually works, then this might possibly even be a cpu bug that we're patching. If you can get someone from AMD to comment on this or give a rationale for why the bug appears and why your fix works, then please post the patch on libc-alpha for review. You may want to follow the checklist here for your patch submission: http://sourceware.org/glibc/wiki/Contribution%20checklist -- 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 prev parent reply other threads:[~2012-10-04 12:31 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 [this message] 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-QN199FkChE@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: linkBe 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).