Bug 1737291
| Summary: | features/locks: avoid use after freed of frame for blocked lock | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Kinglong Mee <kinglongmee> |
| Component: | locks | Assignee: | Kinglong Mee <kinglongmee> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | mainline | CC: | atumball, bugs, spalai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-20 09:36:54 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: | |||
REVIEW: https://review.gluster.org/23155 (features/locks: avoid use after freed of frame for blocked lock) posted (#1) for review on master by Kinglong Mee REVIEW: https://review.gluster.org/23155 (features/locks: avoid use after freed of frame for blocked lock) merged (#2) on master by Amar Tumballi |
Description of problem: The fop contains blocked lock may use freed frame info when other unlock fop has unwind the blocked lock. Because the blocked lock is added to block list in inode lock(or other lock), after that, when out of the inode lock, the fop contains the blocked lock should not use it. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: