Bug 497420 - ipc connect/disconnect in cpg service causes cpg to segfault
Summary: ipc connect/disconnect in cpg service causes cpg to segfault
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openais
Version: 5.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Steven Dake
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 500918
TreeView+ depends on / blocked
 
Reported: 2009-04-23 20:18 UTC by Steven Dake
Modified: 2016-04-26 15:46 UTC (History)
5 users (show)

Fixed In Version: openais-0.80.6-1.el5_4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 11:29:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1366 0 normal SHIPPED_LIVE openais bug-fix and enhancement update 2009-09-01 11:00:17 UTC

Description Steven Dake 2009-04-23 20:18:20 UTC
Description of problem:
this bug was undiscovered by our testing, but Novell found the issue.  This is not a regression, but instead a design error in the cpg service.

Version-Release number of selected component (if applicable):
openais-0.80.3-22.5_3.4

How reproducible:
very rare

Steps to Reproduce:
1.start and stop daemons while starting and stopping ipc connections
2.1 out of 100 or less often cpg will segfault aisexec
3.
  
Actual results:
segfault

Expected results:
no segfault

Additional info:
patch available which resolves problem in integration testing at Novell with our full stack minus gfs2.

Comment 6 errata-xmlrpc 2009-09-02 11:29:57 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-2009-1366.html


Note You need to log in before you can comment on or make changes to this bug.