Bug 1338735

Summary: loc_wipe: fix to clean missing member
Product: [Community] GlusterFS Reporter: Prasanna Kumar Kalever <prasanna.kalever>
Component: libglusterfsclientAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-4.1.3 (or later) Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 03:34:51 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:

Description Prasanna Kumar Kalever 2016-05-23 11:03:58 UTC
Description of problem:
                                            
                                                                                               
    struct _loc {                                                                             
            const char *path;                                                                  
            const char *name;                                                              
            inode_t    *inode;                                                                                              
            inode_t    *parent;                                                                                 
            uuid_t      gfid;                                                                
            uuid_t      pargfid;
    };

member 'name' is left with out freeing in loc_wipe().

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

Comment 1 Vijay Bellur 2016-05-23 11:06:27 UTC
REVIEW: http://review.gluster.org/14504 (loc_wipe: fix to clean missing member) posted (#2) for review on master by Prasanna Kumar Kalever (pkalever)

Comment 2 Amar Tumballi 2018-08-29 03:34:51 UTC
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.