Jeff Layton 0cc11a61b8 nfsd: move blocked lock handling under a dedicated spinlock
Bruce was hitting some lockdep warnings in testing, showing that we
could hit a deadlock with the new CB_NOTIFY_LOCK handling, involving a
rather complex situation involving four different spinlocks.

The crux of the matter is that we end up taking the nn->client_lock in
the lm_notify handler. The simplest fix is to just declare a new
per-nfsd_net spinlock to protect the new CB_NOTIFY_LOCK structures.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
2016-10-24 16:51:21 -04:00
..
2016-10-15 12:09:13 -07:00
2016-10-18 12:30:32 +02:00
2016-10-21 19:06:59 -07:00
2016-10-20 00:06:11 +02:00
2016-10-13 20:28:22 -07:00
2016-09-27 21:20:53 -04:00
2016-06-07 22:07:09 -04:00
2016-09-27 18:47:38 -04:00
2016-06-21 09:23:11 +10:00
2016-10-13 20:28:22 -07:00
2016-07-26 16:19:19 -07:00