Bug 1369397
Summary: | segment fault in changelog_cleanup_dispatchers | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Ryan Ding <ryan.ding> |
Component: | changelog | Assignee: | Ryan Ding <ryan.ding> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | avishwan, bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.10.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-06 17:22:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryan Ding
2016-08-23 09:53:05 UTC
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/ |