Description of problem: changelog_cleanup_dispatchers start to cleanup thread with index 'count', which overstep the array priv->ev_dispatcher, segment fault happen. the cleanup loop should start with index 'count-1'
REVIEW: http://review.gluster.org/15293 (features/changelog: fix a segment fault in changelog_cleanup_dispatchers) posted (#1) for review on master by Anonymous Coward
COMMIT: http://review.gluster.org/15293 committed in master by Aravinda VK (avishwan) ------ commit 1f1850ae79a836f1de783c990e575a0d29e26dee Author: Ryan Ding <ryan.ding> Date: Tue Aug 23 17:42:44 2016 +0800 features/changelog: fix a segment fault in changelog_cleanup_dispatchers the arg 'count' in changelog_cleanup_dispatchers means the thread count to cleanup, so the cleanup loop should start with count-1, not count. change the invoke place also. Change-Id: Ia00853a2e0c5e01e145f60048b1f0ac05f2440ab BUG: 1369397 Signed-off-by: Ryan Ding <ryan.ding> Reviewed-on: http://review.gluster.org/15293 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat> Tested-by: Kotresh HR <khiremat> Reviewed-by: Milind Changire <mchangir> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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.10.0, please open a new bug report. glusterfs-3.10.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://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/