diff options
| author | Trond Myklebust <[email protected]> | 2023-09-05 21:03:28 -0400 |
|---|---|---|
| committer | Anna Schumaker <[email protected]> | 2023-09-13 11:51:11 -0400 |
| commit | e86fcf0820d914389b46658a5a7e8969c3af2d53 (patch) | |
| tree | 393b9e35863224bc3ee44e8e6102f346af9d7611 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | 611fa42dfa9d2f3918ac5f4dd5705dfad81b323d (diff) | |
Revert "SUNRPC: Fail faster on bad verifier"
This reverts commit 0701214cd6e66585a999b132eb72ae0489beb724.
The premise of this commit was incorrect. There are exactly 2 cases
where rpcauth_checkverf() will return an error:
1) If there was an XDR decode problem (i.e. garbage data).
2) If gss_validate() had a problem verifying the RPCSEC_GSS MIC.
In the second case, there are again 2 subcases:
a) The GSS context expires, in which case gss_validate() will force a
new context negotiation on retry by invalidating the cred.
b) The sequence number check failed because an RPC call timed out, and
the client retransmitted the request using a new sequence number,
as required by RFC2203.
In neither subcase is this a fatal error.
Reported-by: Russell Cattelan <[email protected]>
Fixes: 0701214cd6e6 ("SUNRPC: Fail faster on bad verifier")
Cc: [email protected]
Signed-off-by: Trond Myklebust <[email protected]>
Signed-off-by: Anna Schumaker <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions