Bug 1397397

Summary:	glusterfs_ctx_new() initializes the lock, other functions do not need to
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	core	Assignee:	Chinmay Kousik <chinmaykousik1>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs, chinmaykousik1, srangana
Target Milestone:	---	Keywords:	EasyFix, Triaged
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-05-14 09:38:25 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 Niels de Vos 2016-11-22 12:50:53 UTC

Description of problem:
http://review.gluster.org/15842 fixes a locking issue and moves the initialization of the lock into glusterfs_ctx_new(). Other functions that call glusterfs_ctx_new() do not need to initialize the ctx->lock anymore.

Version-Release number of selected component (if applicable):
mainline

Comment 1 Niels de Vos 2017-10-05 10:31:55 UTC

Please have a look at bug 1397419 and the linked patches from there. It could be that those changes address this reported issue already. If that is the case, you can close this bug as a duplicate of 1397419.

Thanks!

Comment 2 Amar Tumballi 2019-05-14 09:38:25 UTC


*** This bug has been marked as a duplicate of bug 1397419 ***

Comment 3 Red Hat Bugzilla 2023-09-14 03:34:51 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days