From deaf8439fc42435988aae6a7b9ab681cc0d36b09 Mon Sep 17 00:00:00 2001 From: Anoop C S Date: Tue, 3 May 2016 17:02:17 +0530 Subject: 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 Reviewed-on: http://review.gluster.org/14189 Smoke: Gluster Build System Reviewed-by: Susant Palai Reviewed-by: Poornima G NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Pranith Kumar Karampuri --- rpc/xdr/src/glusterfs3-xdr.x | 1 + 1 file changed, 1 insertion(+) (limited to 'rpc') diff --git a/rpc/xdr/src/glusterfs3-xdr.x b/rpc/xdr/src/glusterfs3-xdr.x index dcd10cb23b7..eefad57ce80 100644 --- a/rpc/xdr/src/glusterfs3-xdr.x +++ b/rpc/xdr/src/glusterfs3-xdr.x @@ -966,6 +966,7 @@ struct gfs3_compound_rsp { struct gfs3_locklist { struct gf_proto_flock flock; string client_uid<>; + unsigned int lk_flags; struct gfs3_locklist *nextentry; }; -- cgit