nfsd4: setclientid_confirm with unmatched verifier should fail
authorJ. Bruce Fields <bfields@redhat.com>
Wed, 21 Sep 2016 00:55:36 +0000 (20:55 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Mon, 26 Sep 2016 19:20:38 +0000 (15:20 -0400)
commit7d22fc11c7edeeac6f1c3f1ae0edcef4de08c6e0
tree51c6cdd75f7a6b424fc65cd8c72aec630c9746f5
parentebd7c72c63acc3d00944c88cbf96143a8cae179f
nfsd4: setclientid_confirm with unmatched verifier should fail

A setclientid_confirm with (clientid, verifier) both matching an
existing confirmed record is assumed to be a replay, but if the verifier
doesn't match, it shouldn't be.

This would be a very rare case, except that clients following
https://tools.ietf.org/html/rfc7931#section-5.8 may depend on the
failure.

Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c