Bug 712126

Summary: corosync coroipcc doesn't handle case when recvmsg can return 0
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: low Docs Contact:
Priority: medium    
Version: 6.1CC: cluster-maint, djansa, jkortus, sdake
Target Milestone: rc   
Target Release: 6.2   
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:51:07 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
Proposed patch sent to ML none

Description Jan Friesse 2011-06-09 14:43:42 UTC 
Description of problem:
According specification recvmsg can return 0, which means that
connection is closed. We had this check, but limited only for systems
other then Linux. recvmsg can return 0 even on Linux, so check is now
applied on all systems.


Version-Release number of selected component (if applicable):
Corosync master

How reproducible:
Without change in code it's almost impossible

Steps to Reproduce:
1. Run corosync restart in cycle + IPC client connection is cycle
2. After few hundred  years on solar and eclipse IPC will starts eating a lot of CPU and will cycle in recvmsg . Client never exits and loops forever
  
Actual results:
Sometime IPC never exists

Expected results:
IPC exits

Additional info:
Best way to reproduce is to use code change in corosync (sleep before recvmsg, kill corosync)
Comment 1 Jan Friesse 2011-06-09 14:44:09 UTC 
Created attachment 503915 [details]
Proposed patch sent to ML
Comment 3 Jan Friesse 2011-06-13 13:14:54 UTC 
Patch commited in GIT master as 2e5dc5f322a5a852d31f5775debbf51e062695ba
Comment 7 Steven Dake 2011-10-27 18:53:40 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 8 errata-xmlrpc 2011-12-06 11:51:07 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