summaryrefslogtreecommitdiffstats
path: root/fs/locks.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@citi.umich.edu>2007-09-12 21:45:07 +0200
committerJ. Bruce Fields <bfields@citi.umich.edu>2007-10-10 00:32:45 +0200
commit02888f41e9d7fa95d1f5b2f76e0f0af6ea8198cc (patch)
tree29b53806e2be24989d343fa13fdb4d9e6d657361 /fs/locks.c
parentMemory shortage can result in inconsistent flocks state (diff)
downloadlinux-02888f41e9d7fa95d1f5b2f76e0f0af6ea8198cc.tar.xz
linux-02888f41e9d7fa95d1f5b2f76e0f0af6ea8198cc.zip
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 <bfields@citi.umich.edu>
Diffstat (limited to '')
-rw-r--r--fs/locks.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/locks.c b/fs/locks.c
index 6e22c8129a80..c7c69d29a576 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