[Bugs] [Bug 1332501] Mandatory locks are not migrated during lock migration

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14189 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit deaf8439fc42435988aae6a7b9ab681cc0d36b09
Author: Anoop C S <anoopcs at redhat.com>
Date:   Tue May 3 17:02:17 2016 +0530

    core: Honour mandatory lock flags during lock migration

    lk_flags from posix_lock_t structure is the primary key used to
    differentiate locks as either advisory and mandatory type. During
    lock migration this field is not read in getactivelk() call path.
    So in order to copy the exact lock state from source to destination
    it is necessary to include lk_flags within lock_migration_info_t
    structure to maintain accurate state. This change also includes
    minor modifications to setactivelk() call to consider lk_flags
    during lock migration.

    Change-Id: I20a7b6b6a0f3bdac5734cce8a2cd2349eceff195
    BUG: 1332501
    Signed-off-by: Anoop C S <anoopcs at redhat.com>
    Reviewed-on: http://review.gluster.org/14189
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Susant Palai <spalai at redhat.com>
    Reviewed-by: Poornima G <pgurusid at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aFRybIQMkH&a=cc_unsubscribe