Bug 1276638

Summary:	write serialization should be guaranteed for posix mandatory locks
Product:	[Community] GlusterFS	Reporter:	Raghavendra Talur <rtalur>
Component:	locks	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	atumball, bugs, ndevos, pkarampu
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-09 09:54:12 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 Raghavendra Talur 2015-10-30 10:47:20 UTC

Description of problem:

When a mandatory lock request arrives at the posix locks xlator, it should be sent success only when all the conflicting operations(like write) which were already STACK WOUND have been UNWOUND too.  If not, then in the rarest of the cases it may happen that a write from the client which had acquired the lock wins the race against the write which was WOUND but not UNWOUND there by causing loss of data guarantees.

How reproducible:
Very rare, but it a bug nevertheless.

Credits: Raghavendra Gowdappa explained the possibility of this bug.

Comment 1 Amar Tumballi 2019-05-09 09:54:12 UTC

Thanks for the report, and considering the rarity of the bug, and as we had not seen this in last 3+ years, marking it as DEFERRED. We will revisit and pick this if we get time resource/time later.