Bug 1287099 - Race between mandatory lock request and ongoing read/write
Summary: Race between mandatory lock request and ongoing read/write
Status: NEW
Alias: None
Product: GlusterFS
Classification: Community
Component: locks   
(Show other bugs)
Version: mainline
Hardware: All
OS: All
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2015-12-01 13:57 UTC by Anoop C S
Modified: 2016-02-02 12:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Anoop C S 2015-12-01 13:57:09 UTC
Description of problem:

The write call checks for a mandatory lock only once at its start.  It is therefore possible for a mandatory lock request to be granted after this check but before the data is modified. An application may then see file data changed even while a mandatory lock was held.

Similarly, an exclusive mandatory lock may be granted on a file for which a read is on going, but before the read has actually completed, and the reading application may see the file data in a state which should not have been visible to it.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

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