[Bugs] [Bug 1287099] New: Race between mandatory lock request and ongoing read/write

[bugzilla at redhat.com]

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

            Bug ID: 1287099
           Summary: Race between mandatory lock request and ongoing
                    read/write
           Product: GlusterFS
           Version: mainline
         Component: locks
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: achiraya at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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:

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