diff options
| author | Benny Halevy <bhalevy@primarydata.com> | 2014-05-30 09:09:27 -0400 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2014-07-11 13:33:46 +0100 |
| commit | ba1ef838a9e275933683edbd08b6e2226f16e351 (patch) | |
| tree | 4d714983dbd5a90b10dcbdc4a9d52593cc6428d4 /mm | |
| parent | 13ce2ab0f6dc3ce7ee779b204786b7e501ac5c1b (diff) | |
| download | kernel_samsung_smdk4412-ba1ef838a9e275933683edbd08b6e2226f16e351.zip kernel_samsung_smdk4412-ba1ef838a9e275933683edbd08b6e2226f16e351.tar.gz kernel_samsung_smdk4412-ba1ef838a9e275933683edbd08b6e2226f16e351.tar.bz2 | |
nfsd4: use recall_lock for delegation hashing
commit 931ee56c67573eb4e51c8a4e78598d965b8b059e upstream.
This fixes a bug in the handling of the fi_delegations list.
nfs4_setlease does not hold the recall_lock when adding to it. The
client_mutex is held, which prevents against concurrent list changes,
but nfsd_break_deleg_cb does not hold while walking it. New delegations
could theoretically creep onto the list while we're walking it there.
Signed-off-by: Benny Halevy <bhalevy@primarydata.com>
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
[bwh: Backported to 3.2:
- Adjust context
- Also remove a list_del_init() in nfs4_setlease() which would now be
before the corresponding list_add()
- Drop change to nfsd_find_all_delegations(), which doesn't exist]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions