Bug 1375554

Summary: Gluster/upcall API has changed, reducing the chance on memory leaks
Product: [Retired] nfs-ganesha Reporter: Niels de Vos <ndevos>
Component: FSAL_GLUSTERAssignee: Soumya Koduri <skoduri>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.4Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-10 06:02:12 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: 1344714    
Bug Blocks:    

Description Niels de Vos 2016-09-13 12:01:50 UTC
Description of problem:
The new API for consuming upcall events has finalized. http://review.gluster.org/14701 contains the functions that should be used. Check the modified test-cases for examples.

Without this new API there are high chances on generating segmentation faults when NFS-Ganesha and Gluster are not using the same malloc()/free() library calls. By default NFS-Ganesha uses glibc, and Gluster uses its own implementation and will crash when Gluster has features.cache-invalidation enabled.

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

Comment 1 Jiffin 2017-04-10 06:02:12 UTC
The https://review.gerrithub.io/#/c/298501/ patch from Soumya fixes this bug for 2.4. Hence closing this bug