Description of problem: currently glfs_new_from_ctx() does not initialize child_down_count conditional variable, but, glfs_free_from_ctx() destroy this variable. mnt3udp_get_export_subdir_inode() from mount3 calls glfs_free_from_ctx(), so bound to invite problems. This patch avoids the issue. Version-Release number of selected component (if applicable): GlusterFS 3.6.2 How reproducible: N/A Steps to Reproduce: N/A Actual results: pthread_cond_destroy called without proper init. Expected results: It should be initialized. Additional info:
REVIEW: http://review.gluster.org/9857 (libgfapi: initialize child_down_count cond. variable.) posted (#4) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/9857 (libgfapi: initialize child_down_count cond. variable.) posted (#5) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/9857 (libgfapi: initialize child_down_count cond. variable.) posted (#6) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/9857 (libgfapi: initialize child_down_count cond. variable.) posted (#7) for review on master by Humble Devassy Chirammal (humble.devassy)
COMMIT: http://review.gluster.org/9857 committed in master by Niels de Vos (ndevos) ------ commit 0ab4cb8174f478e8f725f13e96f608a6186e8384 Author: Humble Devassy Chirammal <hchiramm> Date: Wed Mar 11 17:19:42 2015 +0530 libgfapi: initialize child_down_count cond. variable. currently glfs_new_from_ctx() does not initialize child_down_count conditional variable, but, glfs_free_from_ctx() destroy this variable. mnt3udp_get_export_subdir_inode() from mount3 calls glfs_free_from_ctx(), so bound to invite problems. This patch avoids the issue. Change-Id: I8c1ed83f0b39248edbb78db25c9434274b538e80 BUG: 1200879 Signed-off-by: Humble Devassy Chirammal <hchiramm> Reviewed-on: http://review.gluster.org/9857 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user