nfsd: don't destroy clients that are busy
authorJeff Layton <jlayton@primarydata.com>
Wed, 30 Jul 2014 12:27:14 +0000 (08:27 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Tue, 5 Aug 2014 14:55:01 +0000 (10:55 -0400)
commitfd699b8a48c0ca36e782cf705794358b3e4b8c25
tree4e38b16b1b979e75f157b3dbe0f03d5beccfe8ca
parentfb94d766af0571ab82d5f63e871a73d985d6d6b0
nfsd: don't destroy clients that are busy

It's possible that we'll have an in-progress call on some of the clients
while a rogue EXCHANGE_ID or DESTROY_CLIENTID call comes in. Be sure to
try and mark the client expired first, so that the refcount is
respected.

This will only be a problem once the client_mutex is removed.

Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c