diff options
| author | Jeff Layton <[email protected]> | 2014-08-12 12:03:49 +0000 |
|---|---|---|
| committer | Jeff Layton <[email protected]> | 2014-08-14 14:07:47 +0000 |
| commit | b84d49f9440b2b039828f3eb114e4bd4ebeb0c54 (patch) | |
| tree | 685156b25d833997ada9caf07bd7f2541efd53bd /drivers/net/xen-netback/interface.c | |
| parent | locks: don't call locks_release_private from locks_copy_lock (diff) | |
| download | kernel-b84d49f9440b2b039828f3eb114e4bd4ebeb0c54.tar.gz kernel-b84d49f9440b2b039828f3eb114e4bd4ebeb0c54.zip | |
locks: don't reuse file_lock in __posix_lock_file
Currently in the case where a new file lock completely replaces the old
one, we end up overwriting the existing lock with the new info. This
means that we have to call fl_release_private inside i_lock. Change the
code to instead copy the info to new_fl, insert that lock into the
correct spot and then delete the old lock. In a later patch, we'll defer
the freeing of the old lock until after the i_lock has been dropped.
Acked-by: J. Bruce Fields <[email protected]>
Signed-off-by: Jeff Layton <[email protected]>
Diffstat (limited to 'drivers/net/xen-netback/interface.c')
0 files changed, 0 insertions, 0 deletions