diff options
| author | Jeff Layton <[email protected]> | 2009-01-22 19:16:04 +0000 |
|---|---|---|
| committer | J. Bruce Fields <[email protected]> | 2009-01-27 22:26:59 +0000 |
| commit | fa82a491275a613b15489aab4b99acecb00958d3 (patch) | |
| tree | 1c5d1f5fb9d6c1870891bf088493541564b93bc9 /fs/btrfs/async-thread.c | |
| parent | nfsd: fix cred leak on every rpc (diff) | |
| download | kernel-fa82a491275a613b15489aab4b99acecb00958d3.tar.gz kernel-fa82a491275a613b15489aab4b99acecb00958d3.zip | |
nfsd: only set file_lock.fl_lmops in nfsd4_lockt if a stateowner is found
nfsd4_lockt does a search for a lockstateowner when building the lock
struct to test. If one is found, it'll set fl_owner to it. Regardless of
whether that happens, it'll also set fl_lmops. Given that this lock is
basically a "lightweight" lock that's just used for checking conflicts,
setting fl_lmops is probably not appropriate for it.
This behavior exposed a bug in DLM's GETLK implementation where it
wasn't clearing out the fields in the file_lock before filling in
conflicting lock info. While we were able to fix this in DLM, it
still seems pointless and dangerous to set the fl_lmops this way
when we may have a NULL lockstateowner.
Signed-off-by: Jeff Layton <[email protected]>
Signed-off-by: J. Bruce Fields <[email protected]>
Diffstat (limited to 'fs/btrfs/async-thread.c')
0 files changed, 0 insertions, 0 deletions