Bug 707862

Summary: Corosync - unaligned access would result in bus error on non x86
Product: Red Hat Enterprise Linux 6 Reporter: Jan Friesse <jfriesse>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: cluster-maint, jkortus, sdake
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-1.4.0-1.el6 Doc Type: Bug Fix
Doc Text:
Do not document
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 11:50:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Align IPC to 8-bit
none
unaligned totemip address access would result in bus error on non-unaligned-safe architectures none

Description Jan Friesse 2011-05-26 08:08:22 UTC
Created attachment 501008 [details]
Align IPC to 8-bit

Description of problem:
Align ipc on 8 byte boundaries

Align all ipc messages on 8 byte boundaries.  This alignment will remove bus
errors on systems that can't access non-byte aligned data and should improve
performance.

Fix problem where unaligned totemip address access would result in bus error on non-unaligned-safe architectures

  
Actual results:
Crash on non x86 (Sparc, PPC, ...)

Expected results:
No crash on non x86

Comment 1 Jan Friesse 2011-05-26 08:09:18 UTC
Created attachment 501009 [details]
unaligned totemip address access would result in bus error on non-unaligned-safe architectures

Comment 2 Jan Friesse 2011-05-26 08:10:56 UTC
In GIT as 5dde373c905410db03304f4ed501a3479e0d5c4b and 556007620d8945a14feef7f38e06f8db8bc8cd81

Comment 12 Jan Friesse 2011-10-31 09:22:55 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:
Do not document

Comment 13 errata-xmlrpc 2011-12-06 11:50:37 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/RHBA-2011-1515.html