J. Bruce Fields 934bd07fae 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>
2021-07-06 20:14:41 -04:00
..
2021-02-23 13:39:45 -08:00
2021-01-25 09:36:28 -05:00
2021-05-07 11:23:41 -07:00
2020-09-25 18:01:26 -04:00
2021-01-24 14:27:17 +01:00
2021-03-22 10:19:02 -04:00
2021-01-25 09:36:28 -05:00
2021-05-18 13:44:04 -04:00
2018-09-25 20:34:54 -04:00