Bug 1271137 - nfs-ganesha: memleak with nfs-ganesha and FSAL glusterfs
nfs-ganesha: memleak with nfs-ganesha and FSAL glusterfs
Product: GlusterFS
Classification: Community
Component: ganesha-nfs (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Kaleb KEITHLEY
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-10-13 04:46 EDT by Saurabh
Modified: 2017-03-08 05:56 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-03-08 05:56:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
valgrind logs (632.23 KB, text/plain)
2015-10-13 04:46 EDT, Saurabh
no flags Details

  None (edit)
Description Saurabh 2015-10-13 04:46:07 EDT
Created attachment 1082301 [details]
valgrind logs

Description of problem:
Executed the nfs-ganesha along with the valgrind. Some memleaks are reported.

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

How reproducible:

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

Actual results:
the results are uploaded in a file

Expected results:
No memleaks

Additional info:
Comment 1 Jiffin 2015-10-19 05:59:09 EDT
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
Comment 3 Kaushal 2017-03-08 05:56:10 EST
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.

Note You need to log in before you can comment on or make changes to this bug.