[Bugs] [Bug 1624701] New: error-out {inode, entry}lk fops with all-zero lk-owner

[bugzilla at redhat.com]

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

            Bug ID: 1624701
           Summary: error-out {inode,entry}lk fops with all-zero lk-owner
           Product: GlusterFS
           Version: mainline
         Component: locks
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org



Description of problem:
    Problem:
    Sometimes we find that developers forget to assign lk-owner for an
    inodelk/entrylk/lk before writing code to wind these fops. locks
    xlator at the moment allows this operation. This leads to multiple
    threads in the same client being able to get locks on the inode
    because lk-owner is same and transport is same. So isolation
    with locks can't be achieved.

    Fix:
    Disallow locks with lk-owner zero.

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.