tree 7722a03d55068e783d0dfe6d98635ab50d2b5bfa
parent bbf25010f1a6b761914430f5fca081ec8c7accd1
author J. Bruce Fields <bfields@citi.umich.edu> 1178838127 -0400
committer J. Bruce Fields <bfields@citi.umich.edu> 1191969165 -0400

locks: reverse order of posix_locks_conflict() arguments

The first argument to posix_locks_conflict() is meant to be a lock request,
and the second a lock from an inode's lock request.  It doesn't really
make a difference which order you call them in, since the only
asymmetric test in posix_lock_conflict() is the check whether the second
argument is a posix lock--and every caller already does that check for
some reason.

But may as well fix posix_test_lock() to call posix_locks_conflict()
with the arguments in the same order as everywhere else.

Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>