diff options
| author | Dai Ngo <dai.ngo@oracle.com> | 2022-01-26 13:13:38 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-08 18:15:29 +0100 |
| commit | 72a16cde6954dcb4cb5efeb9b48ec38831772a9a (patch) | |
| tree | 56eefaeb2c9fe899f4c36d162ea5f7bf93aed4bf /kernel/sysctl_binary.c | |
| parent | 3a345198a7c2d1db2526dc60b77052f75de019d3 (diff) | |
| download | linux-72a16cde6954dcb4cb5efeb9b48ec38831772a9a.tar.gz linux-72a16cde6954dcb4cb5efeb9b48ec38831772a9a.tar.bz2 linux-72a16cde6954dcb4cb5efeb9b48ec38831772a9a.zip | |
nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client.
commit ab451ea952fe9d7afefae55ddb28943a148247fe upstream.
From RFC 7530 Section 16.34.5:
o The server has not recorded an unconfirmed { v, x, c, *, * } and
has recorded a confirmed { v, x, c, *, s }. If the principals of
the record and of SETCLIENTID_CONFIRM do not match, the server
returns NFS4ERR_CLID_INUSE without removing any relevant leased
client state, and without changing recorded callback and
callback_ident values for client { x }.
The current code intends to do what the spec describes above but
it forgot to set 'old' to NULL resulting to the confirmed client
to be expired.
Fixes: 2b63482185e6 ("nfsd: fix clid_inuse on mount with security change")
Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Bruce Fields <bfields@fieldses.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/sysctl_binary.c')
0 files changed, 0 insertions, 0 deletions