diff options
| author | Pranith Kumar K <pkarampu@redhat.com> | 2018-07-03 20:38:23 +0530 |
|---|---|---|
| committer | Pranith Kumar Karampuri <pkarampu@redhat.com> | 2018-07-04 15:04:30 +0000 |
| commit | 16e35706aafbcd710136a33a51881d7ffb2471ca (patch) | |
| tree | 4830f8972d2231d86f0103169b64626ce64b8df5 /glusterfs-api.pc.in | |
| parent | 0bd0e7c2b4508cf0fff68bd14e3947287a17e875 (diff) | |
cluster/afr: Make sure lk-owner is assigned at the time of lock
Problem:
In the new eager-lock implementation lk-owner is assigned after the
'local' is added to the eager-lock list, so there exists a possibility
of lock being sent even before lk-owner is assigned.
Fix:
Make sure to assign lk-owner before adding local to eager-lock list
fixes bz#1598193
Change-Id: I26d1b7bcf3e8b22531f1dc0b952cae2d92889ef2
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
(cherry picked from commit c6f93e422855f656d3a86461a8458f37ad0103eb)
Diffstat (limited to 'glusterfs-api.pc.in')
0 files changed, 0 insertions, 0 deletions