Bug 584089 – ACL module core dumps if management is disabled

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 584089 - ACL module core dumps if management is disabled

Summary:	ACL module core dumps if management is disabled

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	urgent Severity high
Target Milestone:	1.3
Target Release:	---
Assigned To:	Rajith Attapattu
QA Contact:	ppecka
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-04-20 14:34 EDT by Rajith Attapattu
Modified:	2010-10-14 12:01 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Load the 'acl module' while disabling management (using the "-m no" parameter), the broker core was dumped. This was due to the 'mgtObject' not being initialized, hence the subsequent 'if' statements passed and resulted in accessing a null management Object. With this update, the broker core is no longer dumped and loading of the 'acl module' while disabling management works as expected
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-10-14 12:01:29 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Rajith Attapattu 2010-04-20 14:34:22 EDT

Description of problem:
If you load the acl module while disabling management (using -m no) the broker core dumps. This is due to the mgtObject not being initialized, hence the subsequent if statements pass and results in accessing a null management Object.

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


How reproducible:
Always

Steps to Reproduce:
Load the acl module with an acl file and set -m no to disable management.
  
Actual results:
Broker core dumps

Expected results:
Should not core dump.

Comment 1 Rajith Attapattu 2010-04-20 14:56:28 EDT

This is fixed in upstream at rev 936028.

Comment 2 ppecka 2010-05-31 08:50:50 EDT

verified on RHEL 5.5/4.8 - i386/x86_64:

rpm -qa | grep -E '(qpid|ais|sesame)' | sort -n
openais-0.80.6-16.el5_5.1
openais-debuginfo-0.80.6-16.el5_5.1
openais-devel-0.80.6-16.el5_5.1
python-qpid-0.7.946106-1.el5
qpid-cpp-client-0.7.946106-1.el5
qpid-cpp-client-devel-0.7.946106-1.el5
qpid-cpp-client-devel-docs-0.7.946106-1.el5
qpid-cpp-client-ssl-0.7.946106-1.el5
qpid-cpp-server-0.7.946106-1.el5
qpid-cpp-server-cluster-0.7.946106-1.el5
qpid-cpp-server-devel-0.7.946106-1.el5
qpid-cpp-server-ssl-0.7.946106-1.el5
qpid-cpp-server-store-0.7.946106-1.el5
qpid-cpp-server-xml-0.7.946106-1.el5
qpid-java-client-0.7.946106-3.el5
qpid-java-common-0.7.946106-3.el5
qpid-tools-0.7.946106-4.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-27
sesame-0.7.3918-2.el5

--> VERIFIED

Comment 3 Martin Prpič 2010-10-10 05:42:41 EDT

    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:
Load the 'acl module' while disabling management (using the "-m no" parameter), the broker core was dumped. This was due to the 'mgtObject' not being initialized, hence the subsequent 'if' statements passed and resulted in accessing a null management Object. With this update, the broker core is no longer dumped and loading of the 'acl module' while disabling management works as expected

Comment 5 errata-xmlrpc 2010-10-14 12:01:29 EDT

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/RHSA-2010-0773.html

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