Commit:     02888f41e9d7fa95d1f5b2f76e0f0af6ea8198cc
Parent:     84d535ade62b6f8ce852745731ad6200c46b977c
Author:     J. Bruce Fields <[EMAIL PROTECTED]>
AuthorDate: Wed Sep 12 15:45:07 2007 -0400
Committer:  J. Bruce Fields <[EMAIL PROTECTED]>
CommitDate: Tue Oct 9 18:32:45 2007 -0400

    locks: fix flock_lock_file() comment
    This comment wasn't updated when lease support was added, and it makes
    essentially the same mistake that the code made before a recent bugfix.
    Signed-off-by: J. Bruce Fields <[EMAIL PROTECTED]>
 fs/locks.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/fs/locks.c b/fs/locks.c
index 6e22c81..c7c69d2 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -715,8 +715,7 @@ next_task:
 /* Try to create a FLOCK lock on filp. We always insert new FLOCK locks
- * at the head of the list, but that's secret knowledge known only to
- * flock_lock_file and posix_lock_file.
+ * after any leases, but before any posix locks.
  * Note that if called with an FL_EXISTS argument, the caller may determine
  * whether or not a lock was successfully freed by testing the return
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to