Description of problem: We are setting mgmt_v3_timer->timer to NULL after mgmt_v3_timer is deleted which is unnecessary. This issue is caught when we were running glusterd with ASAN. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/19812 (glusterd: setting mgmt_v3_timer->timer to NULL after deleting mgmt_v3_timer) posted (#2) for review on master by Sanju Rakonde
COMMIT: https://review.gluster.org/19812 committed in master by "Sanju Rakonde" <srakonde> with a commit message- glusterd: setting mgmt_v3_timer->timer to NULL after deleting mgmt_v3_timer We are setting mgmt_v3_timer->timer to NULL after mgmt_v3_timer is deleted which is unnecessary. So removing the statement. This issue is caught while running glusterd with ASAN. Change-Id: Ied1f91590a2c64ec1af36d4de9c3febd6cf94bb9 Fixes: bz#1562907 Signed-off-by: Sanju Rakonde <srakonde>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/