forked from Minki/linux
nfsd4: kill warnings on testing stateids with mismatched clientids
It's normal for a client to test a stateid from a previous instance, e.g. after a network partition. Signed-off-by: J. Bruce Fields <bfields@redhat.com> Reviewed-by: Benjamin Coddington <bcodding@redhat.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
This commit is contained in:
parent
6cbfad5f20
commit
663e36f076
@ -5531,15 +5531,8 @@ static __be32 nfsd4_validate_stateid(struct nfs4_client *cl, stateid_t *stateid)
|
||||
if (ZERO_STATEID(stateid) || ONE_STATEID(stateid) ||
|
||||
CLOSE_STATEID(stateid))
|
||||
return status;
|
||||
/* Client debugging aid. */
|
||||
if (!same_clid(&stateid->si_opaque.so_clid, &cl->cl_clientid)) {
|
||||
char addr_str[INET6_ADDRSTRLEN];
|
||||
rpc_ntop((struct sockaddr *)&cl->cl_addr, addr_str,
|
||||
sizeof(addr_str));
|
||||
pr_warn_ratelimited("NFSD: client %s testing state ID "
|
||||
"with incorrect client ID\n", addr_str);
|
||||
if (!same_clid(&stateid->si_opaque.so_clid, &cl->cl_clientid))
|
||||
return status;
|
||||
}
|
||||
spin_lock(&cl->cl_lock);
|
||||
s = find_stateid_locked(cl, stateid);
|
||||
if (!s)
|
||||
|
Loading…
Reference in New Issue
Block a user