We have all the pieces in place to support NFSv4 minor version 1
migration in our client. The client should advertise its support
for migration.
Note that v4.1 migration is untested. There are no servers in the
wild that support NFSv4.1 migration.
Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx>
---
fs/nfs/nfs4proc.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 80afb9f..8d0fab7 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -5876,8 +5876,10 @@ out:
return status;
}
-/*
- * nfs4_proc_exchange_id()
+/**
+ * nfs4_proc_exchange_id - Instantiate client ID
+ * @clp: server state
+ * @cred: RPC credential to use for this call
*
* Returns zero, a negative errno, or a negative NFS4ERR status code.
*
@@ -5892,7 +5894,8 @@ int nfs4_proc_exchange_id(struct nfs_client *clp, struct rpc_cred *cred)
struct nfs41_exchange_id_args args = {
.verifier = &verifier,
.client = clp,
- .flags = EXCHGID4_FLAG_SUPP_MOVED_REFER,
+ .flags = EXCHGID4_FLAG_SUPP_MOVED_REFER |
+ EXCHGID4_FLAG_SUPP_MOVED_MIGR,
};
struct nfs41_exchange_id_res res = {
0
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
