Files
kernel_amazon_mt8127-common/include/linux
Chuck Lever 379fa3e80f nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
commit 059aa734824165507c65fd30a55ff000afd14983 upstream.

Xuan Qi reports that the Linux NFSv4 client failed to lock a file
that was migrated. The steps he observed on the wire:

1. The client sent a LOCK request to the source server
2. The source server replied NFS4ERR_MOVED
3. The client switched to the destination server
4. The client sent the same LOCK request to the destination
   server with a bumped lock sequence ID
5. The destination server rejected the LOCK request with
   NFS4ERR_BAD_SEQID

RFC 3530 section 8.1.5 provides a list of NFS errors which do not
bump a lock sequence ID.

However, RFC 3530 is now obsoleted by RFC 7530. In RFC 7530 section
9.1.7, this list has been updated by the addition of NFS4ERR_MOVED.

Reported-by: Xuan Qi <xuan.qi@oracle.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
2017-06-20 14:04:16 +02:00
..
2015-04-29 10:33:54 +02:00
2013-12-04 10:56:22 -08:00
2016-03-09 15:31:54 -08:00
2013-12-08 07:29:27 -08:00
2015-07-03 19:48:08 -07:00
2014-04-03 12:01:05 -07:00
2014-06-26 15:12:38 -04:00
2014-01-15 15:28:47 -08:00
2016-03-03 15:06:24 -08:00