Bug 1375554 - Gluster/upcall API has changed, reducing the chance on memory leaks
Summary: Gluster/upcall API has changed, reducing the chance on memory leaks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: nfs-ganesha
Classification: Retired
Component: FSAL_GLUSTER
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard:
Depends On: 1344714
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 12:01 UTC by Niels de Vos
Modified: 2017-04-10 06:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-04-10 06:02:12 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.