Files
linux/fs
J. Bruce Fields b842e240f2 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>
2007-10-09 18:32:45 -04:00
..
2007-09-11 17:21:19 -07:00
2007-08-22 19:52:46 -07:00
2007-05-08 11:14:59 -07:00
2007-09-28 15:36:42 -07:00
2007-07-16 09:05:52 -07:00
2007-07-31 15:39:36 -07:00
2007-09-11 17:21:19 -07:00
2007-09-25 08:51:04 -07:00
2007-10-08 12:58:14 -07:00
2007-07-21 17:49:14 -07:00
2007-07-20 08:44:19 -07:00
2007-07-19 10:04:43 -07:00
2007-07-19 10:04:45 -07:00
2007-07-29 17:09:29 -07:00
2007-05-18 13:09:34 -07:00
2007-09-20 13:19:59 -07:00
2007-05-21 09:18:19 -07:00
2007-05-08 11:15:01 -07:00
2007-05-08 11:15:09 -07:00
2007-07-16 09:05:48 -07:00
2007-09-11 11:38:25 -07:00
2007-05-09 06:44:57 +02:00
2007-05-11 08:29:36 -07:00
2007-07-19 10:04:45 -07:00
2007-07-19 10:04:45 -07:00
2007-07-27 08:08:51 +02:00
…
2007-07-27 15:40:13 -07:00
2007-07-10 08:04:15 +02:00
2007-09-20 13:19:59 -07:00
2007-07-16 09:05:46 -07:00