[Bugs] [Bug 1276638] New: write serialization should be guaranteed for posix mandatory locks

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1276638

            Bug ID: 1276638
           Summary: write serialization should be guaranteed for posix
                    mandatory locks
           Product: GlusterFS
           Version: mainline
         Component: locks
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: rtalur at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.