Patch "nfs: Fix "Don't increment lock sequence ID after NFS4ERR_MOVED"" has been added to the 4.9-stable tree

This is a note to let you know that I've just added the patch titled

nfs: Fix "Don't increment lock sequence ID after NFS4ERR_MOVED"

to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
nfs-fix-don-t-increment-lock-sequence-id-after-nfs4err_moved.patch
and it can be found in the queue-4.9 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Chuck Lever <[email protected]>
Date: Thu, 26 Jan 2017 15:14:52 -0500
Subject: nfs: Fix "Don't increment lock sequence ID after NFS4ERR_MOVED"

From: Chuck Lever <[email protected]>

[ Upstream commit 406dab8450ec76eca88a1af2fc15d18a2b36ca49 ]

Lock sequence IDs are bumped in decode_lock by calling nfs_increment_seqid(). nfs_increment_sequid() does not use the seqid_mutating_err() function fixed in commit 059aa7348241 ("Don't increment lock sequence ID after NFS4ERR_MOVED").

---
 fs/nfs/nfs4state.c |    1 +
 1 file changed, 1 insertion(+)

@@ -1079,6 +1079,7 @@ static void nfs_increment_seqid(int stat
 		case -NFS4ERR_BADXDR:
 		case -NFS4ERR_RESOURCE:
 		case -NFS4ERR_NOFILEHANDLE:
+		case -NFS4ERR_MOVED:
 			/* Non-seqid mutating errors */
 			return;
 	};

Patches currently in stable-queue which might be from [email protected] are

queue-4.9/nfs-fix-don-t-increment-lock-sequence-id-after-nfs4err_moved.patch