diff options
author | Jeff Layton <jlayton@redhat.com> | 2018-03-16 16:32:02 +0100 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2018-03-19 21:37:21 +0100 |
commit | 68ef3bc3166468678d5e1fdd216628c35bd1186f (patch) | |
tree | 403d19d2d65cd69779143dc51cb0efbd78ce15c9 /fs/ramfs | |
parent | Linux 4.16-rc2 (diff) | |
download | linux-68ef3bc3166468678d5e1fdd216628c35bd1186f.tar.xz linux-68ef3bc3166468678d5e1fdd216628c35bd1186f.zip |
nfsd: remove blocked locks on client teardown
We had some reports of panics in nfsd4_lm_notify, and that showed a
nfs4_lockowner that had outlived its so_client.
Ensure that we walk any leftover lockowners after tearing down all of
the stateids, and remove any blocked locks that they hold.
With this change, we also don't need to walk the nbl_lru on nfsd_net
shutdown, as that will happen naturally when we tear down the clients.
Fixes: 76d348fadff5 (nfsd: have nfsd4_lock use blocking locks for v4.1+ locks)
Reported-by: Frank Sorenson <fsorenso@redhat.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Cc: stable@vger.kernel.org # 4.9
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/ramfs')
0 files changed, 0 insertions, 0 deletions