[Bugs] [Bug 1338501] New: implement meta-lock/unlock for lock migration

[bugzilla at redhat.com]

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

            Bug ID: 1338501
           Summary: implement meta-lock/unlock for lock migration
           Product: GlusterFS
           Version: 3.8.0
         Component: locks
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: spalai at redhat.com
                CC: bugs at gluster.org, ndevos at redhat.com,
                    pkarampu at redhat.com
        Depends On: 1331720



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

Description of problem:
This bz is created to track the meta lock/unlock implementation. This is needed
to synchronize lock-migration with incoming lock requests.


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 Vijay Bellur on 2016-05-09 01:15:16 MVT ---

REVIEW: http://review.gluster.org/14251 (posix/lock: implement meta-lock/unlock
functionality) posted (#1) for review on master by Susant Palai
(spalai at redhat.com)

--- Additional comment from Vijay Bellur on 2016-05-09 01:15:19 MVT ---

REVIEW: http://review.gluster.org/14252 (dht/metalock: add metalock/unlock)
posted (#1) for review on master by Susant Palai (spalai at redhat.com)

--- Additional comment from Vijay Bellur on 2016-05-09 14:36:54 MVT ---

REVIEW: http://review.gluster.org/14252 (dht/metalock: add metalock/unlock)
posted (#2) for review on master by Susant Palai (spalai at redhat.com)

--- Additional comment from Vijay Bellur on 2016-05-09 14:36:57 MVT ---

REVIEW: http://review.gluster.org/14251 (posix/lock: implement meta-lock/unlock
functionality) posted (#2) for review on master by Susant Palai
(spalai at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1331720
[Bug 1331720] implement meta-lock/unlock for lock migration
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.