NFSv4.2: fix handling of COPY ERR_OFFLOAD_NO_REQ
[ Upstream commit 5690eed941ab7e33c3c3d6b850100cabf740f075 ]
If the client sent a synchronous copy and the server replied with
ERR_OFFLOAD_NO_REQ indicating that it wants an asynchronous
copy instead, the client should retry with asynchronous copy.
Fixes: 539f57b3e0
("NFS handle COPY ERR_OFFLOAD_NO_REQS")
Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
7bc36ac671
commit
9d82a58d2a
@@ -443,8 +443,9 @@ ssize_t nfs42_proc_copy(struct file *src, loff_t pos_src,
|
|||||||
continue;
|
continue;
|
||||||
}
|
}
|
||||||
break;
|
break;
|
||||||
} else if (err == -NFS4ERR_OFFLOAD_NO_REQS && !args.sync) {
|
} else if (err == -NFS4ERR_OFFLOAD_NO_REQS &&
|
||||||
args.sync = true;
|
args.sync != res.synchronous) {
|
||||||
|
args.sync = res.synchronous;
|
||||||
dst_exception.retry = 1;
|
dst_exception.retry = 1;
|
||||||
continue;
|
continue;
|
||||||
} else if ((err == -ESTALE ||
|
} else if ((err == -ESTALE ||
|
||||||
|
Reference in New Issue
Block a user