[Bugs] [Bug 1540882] New: Do lock conflict check correctly for wait-list

[bugzilla at redhat.com]

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

            Bug ID: 1540882
           Summary: Do lock conflict check correctly for wait-list
           Product: GlusterFS
           Version: 4.0
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org
        Depends On: 1540669



+++ This bug was initially created as a clone of Bug #1540669 +++

Description of problem:
    Problem:
    ec_link_has_lock_conflict() is traversing over only owner_list
    but the function is also getting called with wait_list.

    Fix:
    Modify ec_link_has_lock_conflict() to traverse lists correctly.
    Updated the callers to reflect the changes.


Version-Release number of selected component (if applicable):


How reproducible:
Found while code-reading

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2018-01-31 12:11:00 EST ---

REVIEW: https://review.gluster.org/19415 (cluster/ec: Do lock conflict check
correctly for wait-list) posted (#1) for review on master by Pranith Kumar
Karampuri

--- Additional comment from Worker Ant on 2018-02-01 04:07:51 EST ---

COMMIT: https://review.gluster.org/19415 committed in master by "Xavier
Hernandez" <jahernan at redhat.com> with a commit message- cluster/ec: Do lock
conflict check correctly for wait-list

Problem:
ec_link_has_lock_conflict() is traversing over only owner_list
but the function is also getting called with wait_list.

Fix:
Modify ec_link_has_lock_conflict() to traverse lists correctly.
Updated the callers to reflect the changes.

BUG: 1540669
Change-Id: Ibd7ea10f4498e7c2761f9a6faac6d5cb7d750c91
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1540669
[Bug 1540669] Do lock conflict check correctly for wait-list
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.