| Summary: | totemip_parse leaks memory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Steven Dake <sdake> | ||||
| Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.2 | CC: | cluster-maint, jkortus | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | corosync-1.4.1-5.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
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
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 752952 (view as bug list) | Environment: | |||||
| Last Closed: | 2012-06-20 12:22:59 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752952, 756082 | ||||||
| Attachments: |
|
||||||
|
Description
Steven Dake
2011-11-10 20:28:02 UTC
Created attachment 558564 [details]
Backported patch
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 |