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

Bug 1201648

Summary:	Conditionally destroy mutex and conditional variables.
Product:	[Community] GlusterFS	Reporter:	Humble Chirammal <hchiramm>
Component:	libgfapi	Assignee:	Humble Chirammal <hchiramm>
Status:	CLOSED DEFERRED	QA Contact:	Sudhir D <sdharane>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 09:37:15 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 Humble Chirammal 2015-03-13 08:09:59 UTC

Description of problem:

The glfs_free_from_ctx() destroy the mutex and conditional variables. However there is no check which make sure these variables are inited properly. 

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

GlusterFS 3.6.2

How reproducible:

N/A

Steps to Reproduce:

N/A

Actual results:

Unconditional destroy of mutex and conditional variables.

Expected results:

The destroy should happen after making sure the variables are inited.

Additional info:

Comment 1 Anand Avati 2015-03-13 08:12:02 UTC

REVIEW: http://review.gluster.org/9875 (libgfapi: conditionally destroy the mutex and cond.variables.) posted (#1) for review on master by Humble Devassy Chirammal (humble.devassy)

Comment 2 Anand Avati 2015-03-13 08:50:26 UTC

REVIEW: http://review.gluster.org/9875 (libgfapi: conditionally destroy the mutex and cond.variables.) posted (#2) for review on master by Humble Devassy Chirammal (humble.devassy)

Comment 3 Jiffin 2018-11-20 09:37:15 UTC

Above bug does not have any functionality impact. It is just improvement in code. I don't see any dev actively working to fix in upcoming releases. Hence closing it for time being as defered .Please feel free to reopen the bug if needed