Bug 350291 - Unwinding stack on PPC 64 corrupts CR
Summary: Unwinding stack on PPC 64 corrupts CR
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: powerpc
OS: Linux
low
high
Target Milestone: ---
Assignee: David Howells
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 298071 (view as bug list)
Depends On:
Blocks: 335861 420551
TreeView+ depends on / blocked
 
Reported: 2007-10-24 11:30 UTC by Andrew Haley
Modified: 2007-12-11 21:10 UTC (History)
3 users (show)

Fixed In Version: 2.6.23.1-42.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-07 00:43:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Patch to fix the kernel (1.03 KB, patch)
2007-10-25 15:11 UTC, David Howells 		no flags Details | Diff
View All

Description Andrew Haley 2007-10-24 11:30:03 UTC 
During gcc testing we discovered a bug in the kernel unwinder data which causes
the CR register to be corrupted when throwing an exception through the vDSO.

There is a patch applied upstream.

http://gcc.gnu.org/ml/gcc/2007-10/msg00197.html

There is a test case at http://gcc.gnu.org/ml/gcc/2007-10/msg00184.html

This bug is preventing some packages from ebing built.
Comment 2 Andrew Haley 2007-10-25 11:00:37 UTC 
*** Bug 298071 has been marked as a duplicate of this bug. ***
Comment 3 David Howells 2007-10-25 14:08:11 UTC 
This patch looks reasonable to me.
Comment 4 David Howells 2007-10-25 15:11:24 UTC 
Created attachment 237451 [details]
Patch to fix the kernel
Comment 5 Chuck Ebbert 2007-10-25 18:26:09 UTC 
Fedora 8 blocker??
Comment 6 Robert Marcano 2007-10-25 18:48:52 UTC 
It is for me, I can not rebuild eclipse-subclipse por ppc64 users, leaving a
broken upgrade path for them, see Bug #298071
Comment 7 Chuck Ebbert 2007-10-25 20:52:49 UTC 
Okay, in Fedora 8 kernel CVS.
Comment 9 Chuck Ebbert 2007-11-07 00:43:37 UTC 
Fix is in Fedora 8 release.
Comment 10 David Woodhouse 2007-11-14 02:34:07 UTC 
Fixed for FC6 in kernel-2.6.22.12-70.fc6
Note You need to log in before you can comment on or make changes to this bug.