Bug 754184

Summary: Resource leak in dmeventd
Product: Red Hat Enterprise Linux 5 Reporter: Pavel Raiskup <praiskup>
Component: device-mapperAssignee: Zdenek Kabelac <zkabelac>
Status: CLOSED WONTFIX QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 5.8CC: agk, ccaulfie, cmarthal, dwysocha, heinzm, jbrassow, kdudka, ovasik, praiskup, prajnoha, pvrabec, thornber, zkabelac
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:24:46 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
Resource leak in dmeventd fixed. none

Description Pavel Raiskup 2011-11-15 16:19:49 UTC
Description of problem:

Resource leak in dmeventd

=> daemons/dmeventd/dmeventd.c:754

if dm_task_set_uuid() fails, dmt leaks storage it points to.

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

LVM2-CLUSTER.2.02.88

Proposed fix attached.

Comment 1 Pavel Raiskup 2011-11-15 16:21:05 UTC
Created attachment 533790 [details]
Resource leak in dmeventd fixed.

Comment 3 Alasdair Kergon 2011-11-15 16:40:25 UTC
I don't understand - what has dmeventd got to do with lvm2-cluster?

Comment 4 Milan Broz 2011-11-15 16:47:03 UTC
This is already fixed upstream. (As Zdenek introduced it and later fixed :-)

That code is not used in lvm2-cluster but it is part of device-mapper library.

(Coverity should find that bug in three packages lvm2, lvm2-cluster and
device-mapper, only dm is relevant here.)

Comment 14 RHEL Program Management 2012-06-12 00:58:26 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 15 RHEL Program Management 2014-03-07 12:39:12 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 17 Mike McCune 2016-03-28 23:47:57 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 19 RHEL Program Management 2020-12-15 07:24:46 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.