Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause
Corosync is running
Consequence
Corosync leaks small amount of memory in long term runs inside getaddrinfo function
Fix
Free leaked memory by calling freeadrrinfo function
Result
Corosync no longer leaks memory returned by getaddrinfo
Description of problem:
totemip_parse uses getaddrinfo without using an associated freeaddrinfo call.
Version-Release number of selected component (if applicable):
corosync-1.4.1-1.el6
How reproducible:
requires valgrind analysis
Steps to Reproduce:
1.
2.
3.
Actual results:
some minimal amount of memory will be leaked when this api is called. This function is not called often, but is called enough that over several months it could add up.
Expected results:
no leaks with getaddrinfo.
Additional info:
[corosync] [PATCH 1/7] Free mem allocated by getaddrinfo
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Corosync is running
Consequence
Corosync leaks small amount of memory in long term runs inside getaddrinfo function
Fix
Free leaked memory by calling freeadrrinfo function
Result
Corosync no longer leaks memory returned by getaddrinfo
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-2012-0777.html