Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1562907

Summary:	set mgmt_v3_timer->timer to NULL after mgmt_v3_timer is deleted
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-20 18:03:13 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 Sanju 2018-04-02 17:17:40 UTC

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:

Comment 1 Worker Ant 2018-04-02 17:21:49 UTC

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

Comment 2 Worker Ant 2018-04-02 23:36:36 UTC

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>

Comment 3 Shyamsundar 2018-06-20 18:03:13 UTC

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/