Jeff Layton d7a06983a0 locks: fix locks_mandatory_locked to respect file-private locks
As Trond pointed out, you can currently deadlock yourself by setting a
file-private lock on a file that requires mandatory locking and then
trying to do I/O on it.

Avoid this problem by plumbing some knowledge of file-private locks into
the mandatory locking code. In order to do this, we must pass down
information about the struct file that's being used to
locks_verify_locked.

Reported-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Acked-by: J. Bruce Fields <bfields@redhat.com>
2014-03-31 08:24:43 -04:00
..
2012-01-03 22:54:56 -05:00
2011-07-26 16:49:47 -07:00
2014-01-30 16:56:55 -08:00
2014-01-30 16:56:55 -08:00
2014-01-23 16:36:52 -08:00
2014-01-27 21:02:39 -08:00
2013-10-16 21:35:53 -07:00
2012-06-20 14:39:36 -07:00
2014-01-23 16:36:53 -08:00
2014-01-30 16:56:55 -08:00