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:
Upstream commit 50f25d8a4b2d16f4c5e0ef620238688b7a315c7a fixed a memory leak in ares_parse_aaaa_reply in the case IPv6 resolution succeeded. We should be aware of the issue.

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

How reproducible:
valgrind, code inspection

Additional info:
https://github.com/bagder/c-ares/commit/50f25d8a4b2d16f4c5e0ef620238688b7a315c7a

Petr, this bug is solved by the rebase tracked by bz #1077544, can you add qa_ack?

Sorry, there were two leaks and one of them got reverted. The other should still be valid, though:
https://github.com/bagder/c-ares/commit/50f25d8a4b2d16f4c5e0ef620238688b7a315c7a

Can you try with an address that resolves to CNAMEs only? Looking at the code, that should do the trick.

(In reply to Jakub Hrozek from comment #8)
> Sorry, there were two leaks and one of them got reverted. The other should
> still be valid, though:
> https://github.com/bagder/c-ares/commit/
> 50f25d8a4b2d16f4c5e0ef620238688b7a315c7a
> 

Gah, this is the one that got reverted actually. This is the valid one:
https://github.com/bagder/c-ares/commit/bffd67f16a8f42fe6dbf79ab2e39d92eea05c8a6

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-2014-1478.html