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

Bug 1692612

Summary:	Locking issue when restarting bricks
Product:	[Community] GlusterFS	Reporter:	Zhang Huan <zhhuan>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-27 17:18:08 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 Zhang Huan 2019-03-26 03:09:44 UTC

Description of problem:
Found a potential locking issue when reading code.

There are two cases to restart brick, one is when glusterd starts or quorum is met, another is when new peers are joined and quorum is changes. In the later case, sync_lock is not taken, and may cause lock corruption.


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 2019-03-26 03:13:10 UTC

REVIEW: https://review.gluster.org/22417 (glusterd: fix potential locking issue on peer probe) posted (#1) for review on master by Zhang Huan

Comment 2 Worker Ant 2019-03-27 17:18:08 UTC

REVIEW: https://review.gluster.org/22417 (glusterd: fix potential locking issue on peer probe) merged (#2) on master by Amar Tumballi