This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/13184] rwlocks can go into dead lock
- From: "siddhesh at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 04 Oct 2012 12:31:31 +0000
- Subject: [Bug nptl/13184] rwlocks can go into dead lock
- Auto-submitted: auto-generated
- References: <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.