Bug 1287099

Summary:	Race between mandatory lock request and ongoing read/write
Product:	[Community] GlusterFS	Reporter:	Anoop C S <anoopcs>
Component:	locks	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	anoopcs, atumball, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-09 09:57:16 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:

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:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Amar Tumballi 2019-05-09 09:57:16 UTC

Considering we had no reported bug about this in last 3 years, would prefer to mark it DEFERRED, and revisit this depending on time/resource after couple of releases.