Bug 1737291 - features/locks: avoid use after freed of frame for blocked lock
Summary: features/locks: avoid use after freed of frame for blocked lock
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: locks
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Kinglong Mee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-05 03:20 UTC by Kinglong Mee
Modified: 2019-08-20 09:36 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-20 09:36:54 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23155 0 None Merged features/locks: avoid use after freed of frame for blocked lock 2019-08-20 09:36:52 UTC

Description Kinglong Mee 2019-08-05 03:20:44 UTC
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:

Comment 1 Worker Ant 2019-08-05 03:23:00 UTC
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

Comment 2 Worker Ant 2019-08-20 09:36:54 UTC
REVIEW: https://review.gluster.org/23155 (features/locks: avoid use after freed of frame for blocked lock) merged (#2) on master by Amar Tumballi


Note You need to log in before you can comment on or make changes to this bug.