Bug 665165

Summary: shared mem leak if corosync dies unexpectantly
Product: Red Hat Enterprise Linux 6 Reporter: Angus Salkeld <asalkeld>
Component: corosyncAssignee: Angus Salkeld <asalkeld>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0CC: cluster-maint, jkortus, jwest, sdake
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: corosync-1.2.3-23.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:24:15 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: 696735    
Attachments:
Description Flags
fix none

Description Angus Salkeld 2010-12-22 23:26:11 UTC 
Description of problem:

Shared memory is leaked if corosync dies (SIGSEGV/SIGKILL...)
and there are clients connected at the time of corosync's death.

Version-Release number of selected component (if applicable):
all corosync versions

How reproducible:
100%

Steps to Reproduce:
1. start corosync
2. start any corosync client
3. killall -9 corosync
  
Actual results:
ls /dev/shm/*_buffer*
control_buffer-uxrYP7 request_buffer-6AzFFP dispatch_buffer-66Ovlf                                 response_buffer-Xd9vvx

Expected results:
ls /dev/shm/*_buffer*


Additional info:
Comment 1 Angus Salkeld 2010-12-22 23:27:14 UTC 
BTW: The client must be a cpg client.
Comment 2 Angus Salkeld 2010-12-22 23:31:58 UTC 
Created attachment 470342 [details]
fix

patch to fix the problem attached. Will post to ML.
Comment 11 errata-xmlrpc 2011-05-19 14:24:15 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-2011-0764.html