Red Hat Bugzilla – Bug 905941
Fix memory fencing error in unwind-forcedunwind.c
Last modified: 2017-09-15 04:24:25 EDT
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.
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.
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.
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