diff options
| author | Jeff Layton <jlayton@redhat.com> | 2014-02-03 12:13:07 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-12-06 15:55:39 -0800 |
| commit | 2374aee49483447aff3fb330d5e8ee60fa0c9234 (patch) | |
| tree | b7cf4ad967709e15e1828b04fa1dd51b41631d12 /net/unix/sysctl_net_unix.c | |
| parent | 42be4e5c4a5da3f9e27d6e1420612c3aea11f658 (diff) | |
locks: eliminate BUG() call when there's an unexpected lock on file close
commit 8c3cac5e6a85f03602ffe09c44f14418699e31ec upstream.
A leftover lock on the list is surely a sign of a problem of some sort,
but it's not necessarily a reason to panic the box. Instead, just log a
warning with some info about the lock, and then delete it like we would
any other lock.
In the event that the filesystem declares a ->lock f_op, we may end up
leaking something, but that's generally preferable to an immediate
panic.
Acked-by: J. Bruce Fields <bfields@fieldses.org>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Cc: Markus Blank-Burian <burian@muenster.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions