Bug 1213542 - Symlink heal leaks 'linkname' memory
Summary: Symlink heal leaks 'linkname' memory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1216302
TreeView+ depends on / blocked
 
Reported: 2015-04-20 17:55 UTC by Pranith Kumar K
Modified: 2016-06-16 12:53 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of:
: 1216302 (view as bug list)
Environment:
Last Closed: 2016-06-16 12:53:42 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Pranith Kumar K 2015-04-20 17:55:45 UTC 
Description of problem:
While reading code found that the memory allocated for 'linkname' is not 'free'ed.

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


How reproducible:


Steps to Reproduce:
1. Create a symlink while one of the bricks is offline and the symlink heal leaks memory.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Anand Avati 2015-04-20 17:59:54 UTC 
REVIEW: http://review.gluster.org/10305 (cluster/afr: Fix memleak in symlink heal) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 2 Anand Avati 2015-04-22 10:53:58 UTC 
REVIEW: http://review.gluster.org/10305 (cluster/afr,dht: Fix memleak after syncop_readlink) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 3 Anand Avati 2015-04-23 13:55:29 UTC 
COMMIT: http://review.gluster.org/10305 committed in master by Vijay Bellur (vbellur) 
------
commit 838317e199c6cc11ff5e7094552537f03a8f6313
Author: Pranith Kumar K <pkarampu>
Date:   Mon Apr 20 23:23:55 2015 +0530

    cluster/afr,dht: Fix memleak after syncop_readlink
    
    Change-Id: Ia71c14c2c2709c541075748c9011437e0d8cac4b
    BUG: 1213542
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/10305
    Reviewed-by: Ravishankar N <ravishankar>
    Reviewed-by: N Balachandran <nbalacha>
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Reviewed-by: Vijay Bellur <vbellur>
    Tested-by: Vijay Bellur <vbellur>
Comment 4 Nagaprasad Sathyanarayana 2015-10-25 14:48:52 UTC 
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
Comment 5 Nagaprasad Sathyanarayana 2015-10-25 14:54:55 UTC 
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
Comment 6 Niels de Vos 2016-06-16 12:53:42 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.