Bug 1117243 - Found dirent+inode leaks in readdirp in afr
Summary: Found dirent+inode leaks in readdirp in afr
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:
TreeView+ depends on / blocked
 
Reported: 2014-07-08 11:17 UTC by Pranith Kumar K
Modified: 2014-11-11 08:36 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of:
Environment:
Last Closed: 2014-11-11 08:36:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Pranith Kumar K 2014-07-08 11:17:36 UTC
Description of problem:
I found some dirent and inode leaks with afrv2. afr does itransform of these entries by taking it to one more list but doesn't free the list.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-07-08 11:19:20 UTC
REVIEW: http://review.gluster.org/8261 (cluster/afr: Fix dirent leak) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2014-07-14 16:29:25 UTC
COMMIT: http://review.gluster.org/8261 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 7c74e9c24a06c7ae8f29c4980ea8bffecb01a2c9
Author: Pranith Kumar K <pkarampu>
Date:   Tue Jul 8 16:42:02 2014 +0530

    cluster/afr: Fix dirent leak
    
    afr does itransform by taking the list of entries given by client xlator
    to separate list but doesn't free that list.
    
    Change-Id: Ibb4d38b4934b2bb924385c88f9d7942fad933cb9
    BUG: 1117243
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/8261
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Reviewed-by: Ravishankar N <ravishankar>

Comment 3 Niels de Vos 2014-09-22 12:44:39 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:36:49 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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