Bug 643343

Summary: [Intel 6.0 Bug] Dynamic linker failed to align TCB for AVX
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0CC: ebachalo, fweimer, hongjiu.lu, jakub, jane.lv, jvillalo, jwest, luyu, pm-eus, pmuller, rpacheco, schwab, syeghiay
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.12-1.7.el6_0.1 Doc Type: Bug Fix
Doc Text:
On 64-bit x86 systems with support for AVX vector registers, an insufficient alignment of the thread descriptor may have caused an application to crash during symbol resolution. With this update, the "TCB_ALIGNMENT" value has been increased to 32 bytes, and applications no longer crash.
Story Points: ---
Clone Of:
: 643889 (view as bug list) Environment:
Last Closed: 2010-11-10 18:57:40 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: 642584    
Bug Blocks: 643889    

Description RHEL Program Management 2010-10-15 11:04:35 UTC
This bug has been copied from bug #642584 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 4 Jaromir Hradilek 2010-10-15 14:20:34 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
On 64-bit x86 systems with support for AVX vector registers, an insufficient alignment of the thread descriptor may have caused an application to crash during symbol resolution. With this update, the "TCB_ALIGNMENT" value has been increased to 32 bytes, and applications no longer crash.

Comment 8 errata-xmlrpc 2010-11-10 18:57:40 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0872.html