Bug 1517682 - Memory leak in locks xlator
Summary: Memory leak in locks xlator
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: locks
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On: 1515161
Blocks: glusterfs-3.10.8
TreeView+ depends on / blocked
 
Reported: 2017-11-27 08:50 UTC by Xavi Hernandez
Modified: 2018-04-24 00:16 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.10.8
Clone Of: 1515161
Environment:
Last Closed: 2017-12-08 16:46:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Xavi Hernandez 2017-11-27 08:50:19 UTC
+++ This bug was initially created as a clone of Bug #1515161 +++

Description of problem:

There are memory leaks of strings created with gf_strdup() in features/locks xlator.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-11-27 08:52:46 UTC
REVIEW: https://review.gluster.org/18859 (features/locks: Fix memory leaks) posted (#1) for review on release-3.10 by Xavier Hernandez

Comment 2 Worker Ant 2017-11-27 18:12:53 UTC
COMMIT: https://review.gluster.org/18859 committed in release-3.10 by \"Xavier Hernandez\" <jahernan> with a commit message- features/locks: Fix memory leaks

Backport of:
> BUG: 1515161

Change-Id: Ic1d2e17a7d14389b6734d1b88bd28c0a2907bbd6
BUG: 1517682
Signed-off-by: Xavier Hernandez <jahernan>

Comment 3 Shyamsundar 2017-12-08 16:46:32 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-3.10.8, please open a new bug report.

glusterfs-3.10.8 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] http://lists.gluster.org/pipermail/announce/2017-December/000086.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.