nfsd: move fsnotify on client creation outside spinlock
authorJ. Bruce Fields <bfields@redhat.com>
Tue, 25 May 2021 18:53:44 +0000 (14:53 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Wed, 7 Jul 2021 00:14:41 +0000 (20:14 -0400)
commit934bd07fae7e55232845f909f78873ab8678ca74
tree68b559884a88cd5a69be8bb4886ee3fb160a334b
parentf4e44b393389c77958f7c58bf4415032b4cda15b
nfsd: move fsnotify on client creation outside spinlock

This was causing a "sleeping function called from invalid context"
warning.

I don't think we need the set_and_test_bit() here; clients move from
unconfirmed to confirmed only once, under the client_lock.

The (conf == unconf) is a way to check whether we're in that confirming
case, hopefully that's not too obscure.

Fixes: 472d155a0631 "nfsd: report client confirmation status in "info" file"
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c