diff options
author | Benjamin Coddington <bcodding@redhat.com> | 2017-07-21 19:36:25 +0200 |
---|---|---|
committer | Jeff Layton <jlayton@redhat.com> | 2017-07-21 19:57:31 +0200 |
commit | 3953704fde7ec47f452ce6446fb7a0d5dc2f74df (patch) | |
tree | 8d7594335a5942ef8b280e14cafa5a999aa3fab8 /fs/9p | |
parent | fs/locks: Remove fl_nspid and use fs-specific l_pid for remote locks (diff) | |
download | linux-3953704fde7ec47f452ce6446fb7a0d5dc2f74df.tar.xz linux-3953704fde7ec47f452ce6446fb7a0d5dc2f74df.zip |
locks: restore a warn for leaked locks on close
When locks.c moved to using file_lock_context, the check for any locks that
were not released was moved from the __fput() to destroy_inode() path in
commit 8634b51f6ca2 ("locks: convert lease handling to file_lock_context").
This warning has been quite useful for catching bugs, particularly in NFS
where lock handling still sees some churn.
Let's bring back the warning for leaked locks on __fput, as this warning is
much more likely to be seen and reported by users.
Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Diffstat (limited to 'fs/9p')
0 files changed, 0 insertions, 0 deletions