Hi Bruce-
Here's the SETCLIENTID_CONFIRM fix from a couple of weeks ago, and a
separate clean-up patch.
I haven't been able to reproduce the other issue, where the server
hands out different clientid4's for the same nfs_client_id4 string.
The logic in nfsd4_setclientid() appears to be working as designed.
I may have mistaken the clientid4 verifier for the clientid4, but
I didn't save the original network capture, unfortunately.
---
Chuck Lever (2):
NFSD: Use __be32 for variable holding return value
NFSD: SETCLIENTID_CONFIRM returns NFS4ERR_CLID_INUSE too often
fs/nfsd/nfs4state.c | 33 ++++++++++++---------------------
1 files changed, 12 insertions(+), 21 deletions(-)
--
Chuck Lever
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
