diff options
| author | Jeff Layton <jlayton@redhat.com> | 2018-03-18 08:37:03 -0400 |
|---|---|---|
| committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2018-04-10 16:06:22 -0400 |
| commit | 571745935b2ec276345faec81af732fb9f51082b (patch) | |
| tree | a23fe9112ffc8a69b4ef01a5c804e992cdcb906f /fs/minix | |
| parent | 5656610325a926141625e2d5eed1b0ba57a2e4cb (diff) | |
nfs4: wake any lock waiters on successful RECLAIM_COMPLETE
If we have a RECLAIM_COMPLETE with a populated cl_lock_waitq, then
that implies that a reconnect has occurred. Since we can't expect a
CB_NOTIFY_LOCK callback at that point, just wake up the entire queue
so that all the tasks can re-poll for their locks.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs/minix')
0 files changed, 0 insertions, 0 deletions