[Bugs] [Bug 1598193] New: Stale lock with lk-owner all-zeros is observed in some tests
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jul 4 15:04:08 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1598193
Bug ID: 1598193
Summary: Stale lock with lk-owner all-zeros is observed in some
tests
Product: GlusterFS
Version: 4.1
Component: replicate
Assignee: bugs at gluster.org
Reporter: pkarampu at redhat.com
CC: bugs at gluster.org
Depends On: 1597805
+++ This bug was initially created as a clone of Bug #1597805 +++
Description of problem:
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
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Worker Ant on 2018-07-03 12:23:10 EDT ---
REVIEW: https://review.gluster.org/20455 (cluster/afr: Make sure lk-owner is
assigned at the time of lock) posted (#1) for review on master by Pranith Kumar
Karampuri
--- Additional comment from Worker Ant on 2018-07-04 10:39:05 EDT ---
COMMIT: https://review.gluster.org/20455 committed in master by "Pranith Kumar
Karampuri" <pkarampu at redhat.com> with a commit message- 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#1597805
Change-Id: I26d1b7bcf3e8b22531f1dc0b952cae2d92889ef2
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1597805
[Bug 1597805] Stale lock with lk-owner all-zeros is observed in some tests
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list