summaryrefslogtreecommitdiff
path: root/fs/nfsd/nfs4recover.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2010-02-05 20:09:22 (GMT)
committerJ. Bruce Fields <bfields@citi.umich.edu>2010-02-08 21:20:35 (GMT)
commit7e469af97eed947ba9204712601281a69ae8eb6c (patch)
treef4488e393995ae523ed6dea5370ddad7aa1505b5 /fs/nfsd/nfs4recover.c
parentcdd30fa1664e0245fa64330c7cc2ddab7e47c223 (diff)
downloadlinux-fsl-qoriq-7e469af97eed947ba9204712601281a69ae8eb6c.tar.xz
lockd: don't clear sm_monitored on nsm_reboot_lookup
When lockd gets a notify downcall from statd, it'll search its hosts cache and then clear the sm_monitored bit on the host it finds. The idea is apparently to make lockd redo a SM_MON on the next lock request. This is unnecessary and causes the kernel's NSM cache to go out of sync with statd. statd doesn't stop monitoring a host when it gets a SM_NOTIFY and there's no guarantee that another lock will occur after the reclaim and before the unmount. In that event, no SM_UNMON will occur. Signed-off-by: Jeff Layton <jlayton@redhat.com> Reviewed-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'fs/nfsd/nfs4recover.c')
0 files changed, 0 insertions, 0 deletions