Bug 1276638 - write serialization should be guaranteed for posix mandatory locks
write serialization should be guaranteed for posix mandatory locks
Status: NEW
Product: GlusterFS
Classification: Community
Component: locks (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: bugs@gluster.org
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-30 06:47 EDT by Raghavendra Talur
Modified: 2016-01-11 04:13 EST (History)
3 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Raghavendra Talur 2015-10-30 06:47:20 EDT
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.

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