NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
authorTrond Myklebust <trond.myklebust@hammerspace.com>
Sat, 9 Jun 2018 23:10:31 +0000 (19:10 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 3 Aug 2018 05:50:22 +0000 (07:50 +0200)
commitbaad2bf4477003eb27b40a8c608d8af37b187917
treed70b01580543b1eb2827e701a11f63b29828df23
parent42b1df406a296d28f0a86d6a73b4fdca446ae18e
NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY

[ Upstream commit f9312a541050007ec59eb0106273a0a10718cd83 ]

If the server returns NFS4ERR_SEQ_FALSE_RETRY or NFS4ERR_RETRY_UNCACHED_REP,
then it thinks we're trying to replay an existing request. If so, then
let's just bump the sequence ID and retry the operation.

Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs/nfs4proc.c