RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
There are memory leaks on the following files and functions:

* tests/virnettlscontexttest.c: static int testTLSSessionInit(const void 
  opaque)

* src/rpc/virnettlscontext.c: static int   
  virNetTLSContextValidCertificate(virNetTLSContextPtr ctxt,
                                   virNetTLSSessionPtr sess)
                                

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

How reproducible:
Always.


Steps to Reproduce:
1. cd libvirt
2. ./configure && make && make -C tests valgrind
or
./configure && make && make check tests
valgrind -v --leak-check=full ./tests/virnettlscontexttest
  
Actual results:
==22620==
==22620== LEAK SUMMARY:
==22620==    definitely lost: 90,304 bytes in 64 blocks
==22620==    indirectly lost: 342,671 bytes in 4,994 blocks
==22620==      possibly lost: 0 bytes in 0 blocks
==22620==    still reachable: 136,728 bytes in 1,449 blocks
==22620==         suppressed: 0 bytes in 0 blocks

Expected results:
Fix memory leaks.

Additional info:
please see attachment.

Created attachment 521379 [details]
virnettlscontexttest-by-valgrind.log

Patches for upstream and wait for developers review:
http://www.redhat.com/archives/libvir-list/2011-September/msg00263.html
http://www.redhat.com/archives/libvir-list/2011-September/msg00264.html

Alex

Patches have been pushed, Osier, you may move the bug to POST status.

commit db8ffc2dfb0c21eeb179f689252d72b17dea0b94
Author: Alex Jia <ajia>
Date:   Sun Sep 4 23:48:42 2011 +0800

    rpc: avoid memory leak on virNetTLSContextValidCertificate
    
    * src/rpc/virnettlscontext.c: fix memory leak on
      virNetTLSContextValidCertificate.
    

commit 3a89819de81661d1b2058b7bbc21e1d54ed67edf
Author: Alex Jia <ajia>
Date:   Sun Sep 4 23:48:41 2011 +0800

    tests: avoid memory leak on testTLSSessionInit
    
    * tests/virnettlscontexttest: fix memory leak on virnettlscontext test case.

In POST:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00290.html

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/RHBA-2011-1513.html