Trond Myklebust baad2bf447 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>
2018-08-03 07:50:22 +02:00
..
2018-07-08 15:30:51 +02:00
2018-07-17 11:39:26 +02:00
2018-05-30 07:52:35 +02:00
2018-07-03 11:25:03 +02:00
2018-06-05 11:41:54 +02:00
2017-09-04 19:05:15 -04:00
2018-05-16 10:10:25 +02:00