NFSv4.2: support EXCHGID4_FLAG_SUPP_FENCE_OPS 4.2 EXCHANGE_ID flag
RFC 7862 introduced a new flag that either client or server is allowed to set: EXCHGID4_FLAG_SUPP_FENCE_OPS. Client needs to update its bitmask to allow for this flag value. v2: changed minor version argument to unsigned int Signed-off-by: Olga Kornievskaia <kolga@netapp.com> CC: <stable@vger.kernel.org> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
This commit is contained in:

committed by
Anna Schumaker

parent
094eca3719
commit
8c39076c27
@@ -139,6 +139,8 @@
|
||||
|
||||
#define EXCHGID4_FLAG_UPD_CONFIRMED_REC_A 0x40000000
|
||||
#define EXCHGID4_FLAG_CONFIRMED_R 0x80000000
|
||||
|
||||
#define EXCHGID4_FLAG_SUPP_FENCE_OPS 0x00000004
|
||||
/*
|
||||
* Since the validity of these bits depends on whether
|
||||
* they're set in the argument or response, have separate
|
||||
@@ -146,6 +148,7 @@
|
||||
*/
|
||||
#define EXCHGID4_FLAG_MASK_A 0x40070103
|
||||
#define EXCHGID4_FLAG_MASK_R 0x80070103
|
||||
#define EXCHGID4_2_FLAG_MASK_R 0x80070107
|
||||
|
||||
#define SEQ4_STATUS_CB_PATH_DOWN 0x00000001
|
||||
#define SEQ4_STATUS_CB_GSS_CONTEXTS_EXPIRING 0x00000002
|
||||
|
Reference in New Issue
Block a user