| Summary: | Locks on the server do not get cleaned up on fd close | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Pavan Vilas Sondur <pavan> |
| Component: | locks | Assignee: | Pavan Vilas Sondur <pavan> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTNR | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Pavan Vilas Sondur
2010-03-24 06:48:35 UTC
In fact, server is not leaking posix locks. protocol/server does not maintain a lock table for posix locks and passes the flush along and locks translator cleans up accordingly. Same case with release cbk. However, inodelks and entrylks are always explicitly unlocked. Nevertheless, they are cleaned in pl_forget if any are present in the locks translator, which indicates a bug in the user of inodelks/entrylks. Since, protocol/server adds and removes internal locks during lock and unlock requests respectively, there is not really a bug i.e. no locks remain in the lock table of protocol server. Marking this invalid. |