Description of problem:
In 'glfs_h_poll_cache_invalidation', we create a variable used 'up_inode_arg' using calloc (which will not set any mem_acct info for that variable). But in case of any errors during processing, we free it using 'GF_FREE' which makes the process crash with ESEGV which trying to access mem_acct variables.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a 4 node ganesha cluster.
2. Create a volume and enable ganesha on it.
3. Mount the volume using vers=3 or 4 and create nested directories on the mount point.
4. Add bricks to the volume.
gluster volume add-brick newvolume replica 2
5. start the rebalance process:
gluster v rebalance newvolume start force
6. Observe that while rebalance is in progress, ganesha process on the mounted node gets killed with seg fault error:
nfs-ganesha process crashes with ESEGV
nfs-ganesha process shouldn't crash.
This issue is originally reported in bug1339208
REVIEW: http://review.gluster.org/14521 (gfapi/upcall: Use GF_CALLOC while allocating variables) posted (#1) for review on master by soumya k (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/14521 committed in master by Niels de Vos (email@example.com)
Author: Soumya Koduri <firstname.lastname@example.org>
Date: Tue May 24 17:42:06 2016 +0530
gfapi/upcall: Use GF_CALLOC while allocating variables
In 'glfs_h_poll_cache_invalidation', use GF_CALLOC to allocate
'up_inode_arg' to set memory accounting which is used/referred when
freeing the same variable in case of any erros.
Signed-off-by: Soumya Koduri <email@example.com>
Reviewed-by: Kaleb KEITHLEY <firstname.lastname@example.org>
Reviewed-by: jiffin tony Thottan <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Niels de Vos <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.
glusterfs-3.9.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.