tree d6a0f83579e0d7a20a235ddb568d935fe54b24fb
parent 90478939dce096ed5b239cad16237dca0a59d66f
author Jeff Layton <jlayton@redhat.com> 1394459655 -0400
committer Jeff Layton <jlayton@redhat.com> 1396268683 -0400

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>