Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1300924

Summary: Fix mem leaks related to gfapi applications
Product: [Community] GlusterFS Reporter: Soumya Koduri <skoduri>
Component: libgfapiAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.7.7CC: bugs, ndevos, sdharane
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: glusterfs-3.7.7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1295107 Environment:
Last Closed: 2016-04-19 07:52:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1295107, 1311441    
Bug Blocks:    

Description Soumya Koduri 2016-01-22 06:03:06 UTC
+++ This bug was initially created as a clone of Bug #1295107 +++

Description of problem:

This bug is to track the changes required to fix mem leaks related to gfapi applications.

--- Additional comment from Vijay Bellur on 2016-01-04 09:22:51 EST ---

REVIEW: http://review.gluster.org/13125 (inode: Retire the inodes from the lru list in inode_table_destroy) posted (#2) for review on master by soumya k (skoduri)

--- Additional comment from Vijay Bellur on 2016-01-05 00:51:37 EST ---

REVIEW: http://review.gluster.org/13096 (gfapi: Fix inode reference/nlookup counts) posted (#3) for review on master by soumya k (skoduri)

--- Additional comment from Vijay Bellur on 2016-01-11 05:23:23 EST ---

REVIEW: http://review.gluster.org/13096 (gfapi: Fix inode nlookup counts) posted (#4) for review on master by soumya k (skoduri)

--- Additional comment from Vijay Bellur on 2016-01-13 01:13:14 EST ---

REVIEW: http://review.gluster.org/13232 (upcall: free the xdr* allocations) posted (#1) for review on master by soumya k (skoduri)

--- Additional comment from Vijay Bellur on 2016-01-14 06:39:27 EST ---

COMMIT: http://review.gluster.org/13232 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 7d6e5dad15b7ecf2e8abce468aea9fd84b876052
Author: Soumya Koduri <skoduri>
Date:   Wed Jan 13 11:34:27 2016 +0530

    upcall: free the xdr* allocations
    
    Free the xdr string allocations after decoding the upcall
    cache_invalidation request.
    
    Change-Id: I0ffc64f587d6c8566cba76cf08148f937a735926
    BUG: 1295107
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/13232
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 1 Vijay Bellur 2016-01-22 06:04:12 UTC
REVIEW: http://review.gluster.org/13277 (upcall: free the xdr* allocations) posted (#1) for review on release-3.7 by soumya k (skoduri)

Comment 2 Vijay Bellur 2016-01-24 17:13:21 UTC
COMMIT: http://review.gluster.org/13277 committed in release-3.7 by Niels de Vos (ndevos) 
------
commit b313b72ab0bf1fbc92b8b201ea4154ce5fd73c88
Author: Soumya Koduri <skoduri>
Date:   Wed Jan 13 11:34:27 2016 +0530

    upcall: free the xdr* allocations
    
    Free the xdr string allocations after decoding the upcall
    cache_invalidation request.
    
    This is backport of the below fix
       - http://review.gluster.org/13232
    
    Change-Id: I0ffc64f587d6c8566cba76cf08148f937a735926
    BUG: 1300924
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/13232
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/13277
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Kaushal 2016-04-19 07:52:59 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.7.7, please open a new bug report.

glusterfs-3.7.7 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://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user