Description of problem: from snpaview-server, for statfs fops we allocate memory for loc->path directly, instead of using GF_CALLOC/GF_MALLOC, that causes assertion failure and crash if debug mode is enabled during configurations. Version-Release number of selected component (if applicable): mainline How reproducible: 100% Steps to Reproduce: 1.enablde debig mode during building using ./configure --enable-debug 2.create volume start it 3.enable uss 4.create an activate snapshot 5.check getconf NAME_MAX /mnt/.snaps Actual results: this causes mount process to crash Expected results: should not crash mount point Additional info:
REVIEW: http://review.gluster.org/11543 (snapview-client: Allocate memory using GF_CALLOC) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/11543 (snapview-client: Allocate memory using GF_CALLOC) posted (#2) for review on master by mohammed rafi kc (rkavunga)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user