Chuck Lever f07ea10dc8 NFSD: SETCLIENTID_CONFIRM returns NFS4ERR_CLID_INUSE too often
According to RFC 3530bis, the only items SETCLIENTID_CONFIRM processing
should be concerned with is the clientid, clientid verifier, and
principal.  The client's IP address is not supposed to be interesting.

And, NFS4ERR_CLID_INUSE is meant only for principal mismatches.

I triggered this logic with a prototype UCS client -- one that
uses the same nfs_client_id4 string for all servers.  The client
mounted our server via its IPv4, then via its IPv6 address.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
2012-05-31 20:29:45 -04:00
..
2011-01-04 18:22:10 -05:00
2008-02-01 16:42:05 -05:00
2011-07-18 09:39:01 -04:00
2012-05-31 20:29:35 -04:00
2011-11-07 21:10:47 -05:00
2011-11-07 21:10:47 -05:00
2011-11-07 21:10:47 -05:00
2011-07-18 09:39:01 -04:00
2012-01-03 22:55:10 -05:00
2011-03-31 11:26:23 -03:00
2012-05-31 20:29:37 -04:00