| commit | 026722c25e6eb018eab8b9a3c198c258f5b7a2e7 | |
| author | J. Bruce Fields <bfields@citi.umich.edu> | |
| Wed, 18 Mar 2009 19:06:26 +0000 (18 15:06 -0400) | ||
| committer | J. Bruce Fields <bfields@citi.umich.edu> | |
| Wed, 18 Mar 2009 21:38:42 +0000 (18 17:38 -0400) | ||
| tree | b57fa768c7cdaaa21257a57e96427411bf015b0b | treesnapshot (tar.gz zip) |
| parent | 03cf6c9f49a8fea953d38648d016e3f46e814991 | commitdiff |
nfsd4: don't check ip address in setclientid
The spec allows clients to change ip address, so we shouldn't be
requiring that setclientid always come from the same address. For
example, a client could reboot and get a new dhcpd address, but still
present the same clientid to the server. In that case the server should
revoke the client's previous state and allow it to continue, instead of
(as it currently does) returning a CLID_INUSE error.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
The spec allows clients to change ip address, so we shouldn't be
requiring that setclientid always come from the same address. For
example, a client could reboot and get a new dhcpd address, but still
present the same clientid to the server. In that case the server should
revoke the client's previous state and allow it to continue, instead of
(as it currently does) returning a CLID_INUSE error.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
| fs/nfsd/nfs4state.c | diffblobblamehistory |