Bug 1343022 - prevent conflicting meta locks to be accpeted
Summary: prevent conflicting meta locks to be accpeted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: locks
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-06 10:54 UTC by Susant Kumar Palai
Modified: 2019-04-22 15:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-22 15:14:54 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Susant Kumar Palai 2016-06-06 10:54:12 UTC
Description of problem:
Reject meta lock if there is already an active one present.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-06-06 10:59:56 UTC
REVIEW: http://review.gluster.org/14655 (posix/locks: reject conflicting meta locks) posted (#1) for review on master by Susant Palai (spalai)

Comment 2 Vijay Bellur 2016-06-06 11:04:58 UTC
REVIEW: http://review.gluster.org/14655 (posix/locks: reject conflicting meta locks) posted (#2) for review on master by Susant Palai (spalai)

Comment 3 Yaniv Kaul 2019-04-22 14:05:04 UTC
Both were not merged. Status?

Comment 4 Susant Kumar Palai 2019-04-22 15:14:54 UTC
(In reply to Yaniv Kaul from comment #3)
> Both were not merged. Status?

Fixed by https://review.gluster.org/#/c/glusterfs/+/21603/. Closing the bug.


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