diff options
author | J. Bruce Fields <bfields@citi.umich.edu> | 2007-09-13 00:35:15 (GMT) |
---|---|---|
committer | J. Bruce Fields <bfields@citi.umich.edu> | 2007-10-09 22:31:57 (GMT) |
commit | cfdcad4da1903720b9b8c1f176e46a0ebf546be3 (patch) | |
tree | 8c8b12074a5d197c427c4907f41492d556da2dd5 /fs/nfsd/nfs4state.c | |
parent | 1b1a9b3163a83f52ea2ac333846d4dfd2c4edd90 (diff) | |
download | linux-cfdcad4da1903720b9b8c1f176e46a0ebf546be3.tar.xz |
knfsd: nfsv4 delegation recall should take reference on client
It's not enough to take a reference on the delegation object itself; we
need to ensure that the rpc_client won't go away just as we're about to
make an rpc call.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Diffstat (limited to 'fs/nfsd/nfs4state.c')
-rw-r--r-- | fs/nfsd/nfs4state.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c index e706c69..6f182d2 100644 --- a/fs/nfsd/nfs4state.c +++ b/fs/nfsd/nfs4state.c @@ -1345,6 +1345,7 @@ void nfsd_break_deleg_cb(struct file_lock *fl) * lock) we know the server hasn't removed the lease yet, we know * it's safe to take a reference: */ atomic_inc(&dp->dl_count); + atomic_inc(&dp->dl_client->cl_count); spin_lock(&recall_lock); list_add_tail(&dp->dl_recall_lru, &del_recall_lru); @@ -1367,6 +1368,7 @@ void nfsd_break_deleg_cb(struct file_lock *fl) printk(KERN_INFO "NFSD: Callback thread failed for " "for client (clientid %08x/%08x)\n", clp->cl_clientid.cl_boot, clp->cl_clientid.cl_id); + put_nfs4_client(dp->dl_client); nfs4_put_delegation(dp); } } |