| commit | e24dadab08a2a38455434607f52b54a6dc990721 | [log] [tgz] |
|---|---|---|
| author | Jeff Layton <jeff.layton@primarydata.com> | Wed Jan 06 21:28:41 2016 -0500 |
| committer | Jeff Layton <jeff.layton@primarydata.com> | Fri Jan 08 11:38:25 2016 -0500 |
| tree | f9c2c64a27214afa7a8b0d2971b2bc673bfada91 | |
| parent | f27a0fe083bf46fef0d7045aa2e9a7e56e72d8d8 [diff] |
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>