Bug 588894

Summary: memmove causes stack corruption on lossy network
Product: Red Hat Enterprise Linux 5 Reporter: Benjamin Kahn <bkahn>
Component: openaisAssignee: Steven Dake <sdake>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.5CC: casmith, cluster-maint, edamato, jwest, pm-eus, sdake
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: openais-0.80.6-8.el5_4.6 Doc Type: Bug Fix
Doc Text:
A memmove () operation on a high-loss network could have caused possible stack corruption resulting in stack protector abort due to an incorrectly-calculated length in the memmove() operation.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-16 10:17:45 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: 588489    
Bug Blocks:    
Attachments:
Description Flags
backport of revision 2127 none

Description Benjamin Kahn 2010-05-04 19:16:35 UTC
This bug has been copied from bug #588489 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 3 Steven Dake 2010-05-04 20:23:33 UTC
Created attachment 411403 [details]
backport of revision 2127

Comment 6 errata-xmlrpc 2010-06-16 10:17:45 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/RHBA-2010-0485.html

Comment 7 Douglas Silas 2011-01-11 23:17:51 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:
A memmove () operation on a high-loss network could have caused possible stack corruption resulting in stack protector abort due to an incorrectly-calculated length in the memmove() operation.