Description of problem: There are places in code where we fail to destroy already initialized pthread mutexes and condition variabales. This bug is to track those and fix it so that every pthread_mutex_init/pthread_cond_init would have a corresponding pthread_mutex_destroy/pthread_cond_destroy respectively.
REVIEW: https://review.gluster.org/16875 (storage/posix: Destroy pthread mutexes and cond variables in fini()) posted (#1) for review on master by Anoop C S (anoopcs)
REVIEW: https://review.gluster.org/16875 (storage/posix: Destroy pthread mutexes and cond variables in fini()) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: https://review.gluster.org/16875 (storage/posix: Destroy pthread mutexes and cond variables in fini()) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: https://review.gluster.org/16875 (storage/posix: Destroy pthread mutexes and cond variables in fini()) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: https://review.gluster.org/23832 (transport/socket: destroy notify mutex and condition variable) posted (#1) for review on master by None
REVIEW: https://review.gluster.org/23832 (transport/socket: destroy notify mutex and condition variable) merged (#4) on master by Amar Tumballi
This bug is moved to https://github.com/gluster/glusterfs/issues/1071, and will be tracked there from now on. Visit GitHub issues URL for further details