From: Chuck Lever Date: Tue, 15 May 2012 21:42:08 +0000 (-0400) Subject: NFSD: SETCLIENTID_CONFIRM returns NFS4ERR_CLID_INUSE too often X-Git-Tag: v3.5-rc1~18^2~32 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f07ea10dc8f20dfc215b15b012741fcf9f5aa17b;p=pandora-kernel.git 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 Signed-off-by: J. Bruce Fields --- Reading git-diff-tree failed