diff options
| author | Pranith Kumar K <pkarampu@redhat.com> | 2019-04-01 11:53:57 +0530 |
|---|---|---|
| committer | Pranith Kumar Karampuri <pkarampu@redhat.com> | 2019-04-02 12:18:33 +0000 |
| commit | 0a827c1da96302661202e46ea43b6e2526a7ac87 (patch) | |
| tree | fafae8844d92831c7b5c691bc0b22b8667f876a4 /rpc/rpc-transport | |
| parent | d0d3e10d44366c68fc153e48b229e72a4aa26e61 (diff) | |
cluster/afr: Send inodelk/entrylk with non-zero lk-owner
Found missing assignment of lk-owner for an inodelk/entrylk before winding
the 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. To fix it, we need locks xlator change which will disallow
null-lk-owner based inodelk/entrylk/lk. To achieve that we need to first
fix all the places which do this mistake.
updates bz#1624701
Change-Id: Ic3431da3f451a1414f1f4fdcfc4cf41e555f69dd
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Diffstat (limited to 'rpc/rpc-transport')
0 files changed, 0 insertions, 0 deletions