Skip to content

Commit 406dab8

Browse files
chucklevertrondmypd
authored andcommitted
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 059aa73 ("Don't increment lock sequence ID after NFS4ERR_MOVED"). Fixes: 059aa73 ("Don't increment lock sequence ID after ...") Signed-off-by: Chuck Lever <[email protected]> Tested-by: Xuan Qi <[email protected]> Cc: [email protected] # v3.7+ Signed-off-by: Trond Myklebust <[email protected]>
1 parent c929ea0 commit 406dab8

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

fs/nfs/nfs4state.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1091,6 +1091,7 @@ static void nfs_increment_seqid(int status, struct nfs_seqid *seqid)
10911091
case -NFS4ERR_BADXDR:
10921092
case -NFS4ERR_RESOURCE:
10931093
case -NFS4ERR_NOFILEHANDLE:
1094+
case -NFS4ERR_MOVED:
10941095
/* Non-seqid mutating errors */
10951096
return;
10961097
};

0 commit comments

Comments
 (0)