Bug 1663077 - memory leak in mgmt handshake
Summary: memory leak in mgmt handshake
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-03 04:00 UTC by Zhang Huan
Modified: 2019-03-25 16:32 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Clone Of:
Environment:
Last Closed: 2019-03-25 16:32:53 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21981 0 None Merged glusterd: fix memory leak in handshake 2019-01-03 08:50:23 UTC

Description Zhang Huan 2019-01-03 04:00:44 UTC
Description of problem:
Found a memory leak in mgmt handling handshake.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-01-03 04:02:27 UTC
REVIEW: https://review.gluster.org/21981 (glusterd: fix memory leak in handshake) posted (#1) for review on master by Zhang Huan

Comment 2 Worker Ant 2019-01-03 08:50:23 UTC
REVIEW: https://review.gluster.org/21981 (glusterd: fix memory leak in handshake) posted (#1) for review on master by Zhang Huan

Comment 3 Shyamsundar 2019-03-25 16:32:53 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.