Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 769224 - memory leak when run 'virsh domxml-to-native'
memory leak when run 'virsh domxml-to-native'
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.3
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Alex Jia
Virtualization Bugs
:
: 769225 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-20 05:35 EST by Alex Jia
Modified: 2012-06-20 02:39 EDT (History)
8 users (show)

See Also:
Fixed In Version: libvirt-0.9.9-1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 02:39:27 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 15:31:38 EDT

  None (edit)
Description Alex Jia 2011-12-20 05:35:25 EST
Description of problem:
A quite big leak on cmdDomXMLToNative function.

Version-Release number of selected component (if applicable):
# rpm -qf /usr/bin/virsh
libvirt-client-0.9.8-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. virsh dumpxml ${guest} > foo.xml
2. valgrind -v --leak-check=full virsh domxml-to-native qemu-argv foo.xml
3. check 'LEAK SUMMARY' section
  
Actual results:

==7409== 8,193 bytes in 1 blocks are definitely lost in loss record 31 of 33
==7409==    at 0x4A05FDE: malloc (vg_replace_malloc.c:236)
==7409==    by 0x4A06167: realloc (vg_replace_malloc.c:525)
==7409==    by 0x4C7510B: virReallocN (memory.c:161)
==7409==    by 0x4C84679: virFileReadLimFD (util.c:394)
==7409==    by 0x4C84815: virFileReadAll (util.c:455)
==7409==    by 0x41A7AF: cmdDomXMLToNative (virsh.c:5578)
==7409==    by 0x414892: vshCommandRun (virsh.c:16463)
==7409==    by 0x425633: main (virsh.c:17970)
==7409==
==7409== LEAK SUMMARY:
==7409==    definitely lost: 8,193 bytes in 1 blocks
==7409==    indirectly lost: 0 bytes in 0 blocks
==7409==      possibly lost: 0 bytes in 0 blocks
==7409==    still reachable: 127,128 bytes in 1,347 blocks

Expected results:
avoid memory leak.

Additional info:
Comment 1 Alex Jia 2011-12-20 05:36:21 EST
Patch for upstream:
http://www.redhat.com/archives/libvir-list/2011-December/msg00875.html
Comment 2 Eric Blake 2011-12-20 16:46:53 EST
commit ea964658af7a54216e3c7c3ee2e0d2ea719ba018
Author: Alex Jia <ajia@redhat.com>
Date:   Tue Dec 20 18:33:52 2011 +0800

    virsh: plug mem leaks in domxml-*-native
    
    Detected by valgrind. Leaks introduced in commit 4d5383f.
    
    * tools/virsh.c: fix memory leaks on cmdDomXMLFromNative and cmdDomXMLToNative. 
    * how to reproduce?
    
      % virsh dumpxml ${guest} > foo.xml
      % valgrind -v --leak-check=full virsh domxml-from-native qemu-argv foo.xml
      % valgrind -v --leak-check=full virsh domxml-to-native qemu-argv foo.xml
Comment 3 Eric Blake 2011-12-20 16:47:36 EST
*** Bug 769225 has been marked as a duplicate of this bug. ***
Comment 4 Eric Blake 2011-12-20 16:48:19 EST
(In reply to comment #3)
> *** Bug 769225 has been marked as a duplicate of this bug. ***

Be sure to also test domxml-from-native when verifying this bug, since it was a single patch for both leaks.
Comment 6 xhu 2012-01-10 03:32:03 EST
Reproduce it with libvirt-0.9.8-1.el6.x86_64.
Verify it with libvirt-0.9.9-1.el6 and it passed.
Comment 8 errata-xmlrpc 2012-06-20 02:39:27 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0748.html

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