Bug 1284419 - Resource leak in marker
Summary: Resource leak in marker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: marker
Version: mainline
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Manikandan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1284850
TreeView+ depends on / blocked
 
Reported: 2015-11-23 10:10 UTC by Manikandan
Modified: 2016-09-20 04:29 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of:
: 1284850 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:46:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Manikandan 2015-11-23 10:10:40 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Manikandan 2015-11-23 10:12:35 UTC
There is a resource leak in marker code, marker_readdirp_cbk().

Comment 2 Vijay Bellur 2015-11-23 10:38:52 UTC
REVIEW: http://review.gluster.org/12719 (marker : fixing memory leak issue in marker) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 3 Vijay Bellur 2015-11-23 19:03:28 UTC
COMMIT: http://review.gluster.org/12719 committed in master by Vijay Bellur (vbellur) 
------
commit f2287d00c7dc9c088860c12191ff760586889dde
Author: Manikandan Selvaganesh <mselvaga>
Date:   Mon Nov 23 15:58:42 2015 +0530

    marker : fixing memory leak issue in marker
    
    In marker_readdirp_cbk, variable resolvedpath is not properly freed
    and because of which there was a memory leak. The patch fixes it.
    
    Change-Id: I9d80f72e3551aa912369257da3e8e2b261a2067f
    BUG: 1284419
    Signed-off-by: Manikandan Selvaganesh <mselvaga>
    Reviewed-on: http://review.gluster.org/12719
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Niels de Vos 2016-06-16 13:46:08 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.8.0, please open a new bug report.

glusterfs-3.8.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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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