Bug 455435

Summary: x86: user_regset_view table fix for ia32 on 64-bit
Product: Red Hat Enterprise Linux 5 Reporter: Prarit Bhargava <prarit>
Component: kernelAssignee: Prarit Bhargava <prarit>
Status: CLOSED NOTABUG QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: low    
Version: 5.3CC: roland
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-21 20:37:50 UTC Type: ---
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:    
Bug Blocks: 455409    
Attachments:
Description Flags
Upstream fix for this issue none

Description Prarit Bhargava 2008-07-15 14:19:36 UTC 
Backport

Gitweb:    
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1f465f4e475454b8bb590846c50a9d16e8046f3d
Commit:     1f465f4e475454b8bb590846c50a9d16e8046f3d
Parent:     afc85343807bc2c488b7372cd7547875dfe03fe5
Author:     Roland McGrath <roland>
AuthorDate: Fri May 9 15:43:44 2008 -0700
Committer:  Ingo Molnar <mingo>
CommitDate: Tue May 13 19:40:20 2008 +0200

    x86: user_regset_view table fix for ia32 on 64-bit
    
    The user_regset_view table for the 32-bit regsets on the 64-bit build had
    the wrong sizes for the FP regsets.  This bug had no user-visible effect
    (just on kernel modules using the user_regset interfaces and the like).
    But the fix is trivial and risk-free.
    
    Signed-off-by: Roland McGrath <roland>
    Signed-off-by: Ingo Molnar <mingo>
Comment 1 Prarit Bhargava 2008-07-15 14:19:36 UTC 
Created attachment 311838 [details]
Upstream fix for this issue
Comment 2 Prarit Bhargava 2008-07-21 12:56:46 UTC 
Roland, could you comment on whether or not this patch is needed in RHEL5?

Thanks,

P.
Comment 3 Roland McGrath 2008-07-21 20:14:28 UTC 
RHEL5 never had this bug, it was introduced during the refactoring for upstream.