Red Hat Bugzilla – Bug 1271137
nfs-ganesha: memleak with nfs-ganesha and FSAL glusterfs
Last modified: 2017-03-08 05:56:10 EST
Created attachment 1082301 [details]
Description of problem:
Executed the nfs-ganesha along with the valgrind. Some memleaks are reported.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a volume of type 6x2
2. start nfs-ganesha with valgrind
valgrind -v --tool=memcheck --error-limit=no --leak-check=full --show-reachable=yes --log-file=/tmp/ganesha-val0.log /usr/bin/ganesha.nfsd -L /var/log/ganesha.log -f /etc/ganesha/ganesha.conf -N NIV_EVENT
3. on the mount-point start executing the iozone
the results are uploaded in a file
The memleak related to glusterfs is seems to ok. It happens during graph switch()[called from notify function in api/src/glfs-master.c], every variable allocated from that function should be freed from glfs_fini(). And glfs_fini() will be called when a volume is unexported.
Ganesha related memleaks caused from main() function. It seems to there is no proper clean up has done for the same. I will check with Frank and give update on the same
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.