Bug 1430623
Summary: | pthread mutexes and condition variables are not destroyed | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Anoop C S <anoopcs> |
Component: | core | Assignee: | Anoop C S <anoopcs> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | mainline | CC: | bugs, jahernan, moagrawa, rabhat, rkavunga |
Target Milestone: | --- | Keywords: | EasyFix, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-12 14:49: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
Anoop C S
2017-03-09 07:12:44 UTC
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 |