Bug 620837

Summary:	libvirt leaks one string for each host bridge interface definition that has a non-default delay
Product:	Red Hat Enterprise Linux 6	Reporter:	Laine Stump <laine>
Component:	libvirt	Assignee:	Laine Stump <laine>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	dallan, eblake, mjenner, syeghiay, xen-maint, yoyzhang
Target Milestone:	rc	Keywords:	RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	libvirt-0_8_1-21_el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	630623 (view as bug list)		Environment:
Last Closed:	2010-11-11 14:50:39 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:
Bug Depends On:
Bug Blocks:	630623

Description Laine Stump 2010-08-03 15:42:21 UTC

This bug was found by examination of the source. During freeing of the data structure used to hold the definition for host bridge interfaces (those created via the iface-define command), a free of the delay string was inadvertently omitted.

Comment 2 Laine Stump 2010-08-03 15:56:30 UTC

This has been committed upstream 6328dfcb670953c17e6061fae02417f8756726bb

The same patch has also been posted for RHEL6.

Comment 3 RHEL Program Management 2010-08-03 16:07:47 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 4 Dave Allan 2010-08-05 14:17:21 UTC

libvirt-0_8_1-21_el6 has been built in RHEL-6-candidate with the fix.

Dave

Comment 7 releng-rhel@redhat.com 2010-11-11 14:50:39 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.