SUNRPC: The transmitted message must lie in the RPCSEC window of validity
authorTrond Myklebust <trond.myklebust@hammerspace.com>
Tue, 14 Aug 2018 17:50:21 +0000 (13:50 -0400)
committerTrond Myklebust <trond.myklebust@hammerspace.com>
Sun, 30 Sep 2018 19:35:13 +0000 (15:35 -0400)
commit3021a5bbbf0aa0252f2993b84ee903a0eca0b690
treebf303cbc4c0a4f7e9b51b8944202ed43cf953b35
parent9ee94d3ed6a4f75dbf0a022927021a42a24dbdf8
SUNRPC: The transmitted message must lie in the RPCSEC window of validity

If a message has been encoded using RPCSEC_GSS, the server is
maintaining a window of sequence numbers that it considers valid.
The client should normally be tracking that window, and needs to
verify that the sequence number used by the message being transmitted
still lies inside the window of validity.

So far, we've been able to assume this condition would be realised
automatically, since the client has been encoding the message only
after taking the socket lock. Once we change that condition, we
will need the explicit check.

Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
include/linux/sunrpc/auth.h
include/linux/sunrpc/auth_gss.h
net/sunrpc/auth.c
net/sunrpc/auth_gss/auth_gss.c
net/sunrpc/clnt.c
net/sunrpc/xprt.c