Description of problem: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fce642eb420 in pthread_mutex_lock () from ./lib64/libpthread.so.0 (gdb) bt #0 0x00007fce642eb420 in pthread_mutex_lock () from ./lib64/libpthread.so.0 #1 0x00007fce52ee2e13 in br_stub_worker (data=0x7fce54010f90) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/xlators/features/bit-rot/src/stub/bit-rot-stub-helpers.c:337 #2 0x00007fce642e9a51 in start_thread () from ./lib64/libpthread.so.0 #3 0x00007fce63c5393d in clone () from ./lib64/libc.so.6 (gdb) fr 1 #1 0x00007fce52ee2e13 in br_stub_worker (data=0x7fce54010f90) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/xlators/features/bit-rot/src/stub/bit-rot-stub-helpers.c:337 337 /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/xlators/features/bit-rot/src/stub/bit-rot-stub-helpers.c: No such file or directory. (gdb) info locals priv = 0x0 this = 0x7fce54010f90 stub = 0x0 ret = 0 init may not have initialized this->private by the time br_stub_worker starts running, leading to NULL dereference. Version-Release number of selected component (if applicable): How reproducible: This is observed at https://build.gluster.org/job/rackspace-regression-2GB-triggered/16180/consoleFull Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/12754 (features/bit-rot: Fix NULL dereference) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/12754 (features/bit-rot: Fix NULL dereference) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/12754 committed in master by Venky Shankar (vshankar) ------ commit a1919e91279a6c691fbd3dd6c0d97e74e78ccf22 Author: Pranith Kumar K <pkarampu> Date: Thu Nov 26 09:58:39 2015 +0530 features/bit-rot: Fix NULL dereference Problem: By the time br_stub_worker is accessing this->private in it's thread, 'init' may not have set 'this->private = priv'. This leads to NULL dereference leading to brick crash. Fix: Set this->private before launching these threads. Change-Id: Ic797eb195fdd0c70d19f28d0b97bc0181fd3dd2f BUG: 1285616 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/12754 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Venky Shankar <vshankar>
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