+++ This bug was initially created as a clone of Bug #1240184 +++ 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: --- Additional comment from Anand Avati on 2015-07-06 03:28:55 EDT --- REVIEW: http://review.gluster.org/11543 (snapview-client: Allocate memory using GF_CALLOC) posted (#1) for review on master by mohammed rafi kc (rkavunga) --- Additional comment from Anand Avati on 2015-07-06 06:59:17 EDT --- REVIEW: http://review.gluster.org/11543 (snapview-client: Allocate memory using GF_CALLOC) posted (#2) for review on master by mohammed rafi kc (rkavunga)
upstream master : http://review.gluster.org/#/c/11543/ upstream release 3.7 : http://review.gluster.org/#/c/11743/
upstream master : http://review.gluster.org/#/c/11543/ upstream release 3.7 : http://review.gluster.org/#/c/11743/ RHGS URL: https://code.engineering.redhat.com/gerrit/#/c/55152/
This bug depends on the regression run for uss. So once the regression is complete without any issues, we will mark it as verified.
Since USS regression passed successfully and no major issues are seen. hence marking this bug as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1845.html