Description of problem: a memmove on openais can cause stack corruption on a highly lossy network Version-Release number of selected component (if applicable): openais-0.80.6 How reproducible: 100% Steps to Reproduce: 1. generate 90% packet loss (by instrumenting source code) 2. start 8 nodes with cpgverify 3. kill 1 node Actual results: crashes Expected results: no crash Additional info:
Created attachment 411105 [details] patch that fixes stack corruption.
Is there a way to verify this without instrumenting the code?
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.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -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.+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.
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-2011-0100.html