Bug 1201648 - Conditionally destroy mutex and conditional variables.
Summary: Conditionally destroy mutex and conditional variables.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Humble Chirammal
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-13 08:09 UTC by Humble Chirammal
Modified: 2018-11-20 09:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-20 09:37:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.