diff options
| author |   Jeff Layton <jeff.layton@primarydata.com> | 2015-07-11 06:43:03 -0400 |
|---|---|---|
| committer | Jeff Layton <jeff.layton@primarydata.com> | 2015-07-13 06:29:11 -0400 |
| commit | 83bfff23e9ed19f37c4ef0bba84e75bd88e5cf21 (patch) | |
| tree | e8b8f8238118d2d3c16f3f83625223377b9719ee /fs/locks.c | |
| parent | locks: new helpers - flock_lock_inode_wait and posix_lock_inode_wait (diff) | |
| download | linux-dev-83bfff23e9ed19f37c4ef0bba84e75bd88e5cf21.tar.xz linux-dev-83bfff23e9ed19f37c4ef0bba84e75bd88e5cf21.zip | |
nfs4: have do_vfs_lock take an inode pointer
Now that we have file locking helpers that can deal with an inode
instead of a filp, we can change the NFSv4 locking code to use that
instead.
This should fix the case where we have a filp that is closed while flock
or OFD locks are set on it, and the task is signaled so that it doesn't
wait for the LOCKU reply to come in before the filp is freed. At that
point we can end up with a use-after-free with the current code, which
relies on dereferencing the fl_file in the lock request.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Reviewed-by: "J. Bruce Fields" <bfields@fieldses.org>
Tested-by: "J. Bruce Fields" <bfields@fieldses.org>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions