Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 905941

Summary: Fix memory fencing error in unwind-forcedunwind.c
Product: Red Hat Enterprise Linux 6 Reporter: Jeff Law <law>
Component: glibcAssignee: Siddhesh Poyarekar <spoyarek>
Status: CLOSED ERRATA QA Contact: Arjun Shankar <ashankar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: ashankar, fweimer, jburke, jstancek, law, mfranc, mnewsome, pfrankli, qcai, spoyarek, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.12-1.146.el6 Doc Type: Bug Fix
Doc Text:
This update fixes a sporadic crash in pthreads during stack unwinding on thread cancellation on PowerPC.
Story Points: ---
Clone Of: 852445
: 906079 1103874 (view as bug list) Environment:
Last Closed: 2014-10-14 04:41:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 852445    
Bug Blocks: 906079, 1056252, 1103874    

Comment 4 Jeff Law 2013-01-30 21:15:42 UTC
It hasn't yet.  And (of course) the plan is to go upstream, then backport (assuming this BZ gets a full set of acks).  I just keep getting hijacked by other small stuff that's accumulated over time.

Comment 5 RHEL Program Management 2013-02-03 06:47:45 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 8 Jeff Law 2014-03-14 03:20:19 UTC
I do :-)  They stalled going upstream as reviews showed the ARM port has similar problems and I simply wasn't arm-aware enough to write those bits.


https://sourceware.org/ml/libc-alpha/2013-01/msg00538.html
https://sourceware.org/ml/libc-alpha/2013-02/msg00050.html

Are the two threads and should have a thorough analysis as well as the PPC patches.  They'll probably start to look familiar since you helped with the analysis.

Comment 13 errata-xmlrpc 2014-10-14 04:41:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-1391.html