nfs: Fix "Don't increment lock sequence ID after NFS4ERR_MOVED"
authorChuck Lever <chuck.lever@oracle.com>
Thu, 26 Jan 2017 20:14:52 +0000 (15:14 -0500)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Thu, 26 Jan 2017 20:25:03 +0000 (15:25 -0500)
commit406dab8450ec76eca88a1af2fc15d18a2b36ca49
treed08c598a64c13f71744a99ff789fd87047387ff5
parentc929ea0b910355e1876c64431f3d5802f95b3d75
nfs: Fix "Don't increment lock sequence ID after NFS4ERR_MOVED"

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").

Fixes: 059aa7348241 ("Don't increment lock sequence ID after ...")
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Tested-by: Xuan Qi <xuan.qi@oracle.com>
Cc: stable@vger.kernel.org # v3.7+
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4state.c