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
..
2014-07-08 17:14:27 -04:00
2016-10-07 18:46:30 -07:00
2016-08-04 19:59:06 -04:00
2016-03-18 11:42:53 -04:00
2014-08-17 12:00:12 -04:00
2016-10-07 14:54:25 -04:00
2016-10-07 14:54:25 -04:00
2016-01-22 18:04:28 -05:00
2016-07-13 15:53:41 -04:00
2016-09-26 15:20:36 -04:00
2016-05-29 19:08:00 -04:00
2016-01-14 17:32:51 -05:00
2016-10-07 14:54:25 -04:00
2016-10-07 14:54:25 -04:00
2016-10-07 14:54:25 -04:00