Bug 176343

Summary: rg_test fails on x86_64
Product: [Retired] Red Hat Cluster Suite Reporter: Corey Marthaler <cmarthal>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rgmanager-1.9.46-0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-12 17:11:13 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:
Attachments:
Description Flags
Fixes behavior none

Description Corey Marthaler 2005-12-21 16:44:02 UTC 
Description of problem:
It failed to detect that I had IPs being used for different services (user
error) which then allowed the services to fail to relocate.

Version-Release number of selected component (if applicable):
[root@taft-02 ~]# rpm -q rgmanager
rgmanager-1.9.44-0
Comment 1 Lon Hohberger 2005-12-21 17:00:54 UTC 
Heh, actually, the stock version with 1.9.44 fails to run - it segfaults on
startup. ;)

The version I installed works ;)
Comment 2 Lon Hohberger 2005-12-21 17:02:49 UTC 
Created attachment 122498 [details]
Fixes behavior

Preliminary patch.  This makes it work, but reduces the usefulness of
liblalloc's stack checking.  The correct fix is to figure out why accessing
__builtin_return_address(x) causes a segfault on x86_64.
Comment 3 Lon Hohberger 2006-01-04 17:05:56 UTC 
The liblalloc's stack checking is architecture dependent. 
__builtin_return_address(x) for x>0 is never guaranteed to work on any
architecture; that it has in the past should be no indication of future performance.