locks: prink more detail when there are leaked locks
authorJeff Layton <jeff.layton@primarydata.com>
Thu, 7 Jan 2016 02:28:41 +0000 (21:28 -0500)
committerJeff Layton <jeff.layton@primarydata.com>
Fri, 8 Jan 2016 16:38:25 +0000 (11:38 -0500)
commite24dadab08a2a38455434607f52b54a6dc990721
treef9c2c64a27214afa7a8b0d2971b2bc673bfada91
parentf27a0fe083bf46fef0d7045aa2e9a7e56e72d8d8
locks: prink more detail when there are leaked locks

Right now, we just get WARN_ON_ONCE, which is not particularly helpful.
Have it dump some info about the locks and the inode to make it easier
to track down leaked locks in the future.

Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Acked-by: "J. Bruce Fields" <bfields@fieldses.org>
fs/locks.c