Red Hat Bugzilla – Bug 1276638
write serialization should be guaranteed for posix mandatory locks
Last modified: 2016-01-11 04:13:00 EST
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.
Very rare, but it a bug nevertheless.
Credits: Raghavendra Gowdappa explained the possibility of this bug.