Bug 862566
Summary: | ares_parse_aaaa_reply can leak memory | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jakub Hrozek <jhrozek> |
Component: | c-ares | Assignee: | Jakub Hrozek <jhrozek> |
Status: | CLOSED ERRATA | QA Contact: | Jakub Prokes <jprokes> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | dpal, jhrozek, jprokes, psklenar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | c-ares-1.10.0-1.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-14 06:44:36 UTC | Type: | Bug |
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: | 1061410 |
Description
Jakub Hrozek
2012-10-03 08:54:27 UTC
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 |