summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorJeff Layton <jlayton@kernel.org>2018-08-08 19:54:09 +0300
committerJeff Layton <jlayton@kernel.org>2018-08-08 19:59:06 +0300
commitda33a871ba178dbe81da7d755818d3c2088cae32 (patch)
treec0298c6e59bdc6ee3646a9f8e7cdf0aa55f32cec /fs
parent96c25b777442d3a875b1921b1f047ea00d96c8ea (diff)
downloadlinux-da33a871ba178dbe81da7d755818d3c2088cae32.tar.xz
locks: remove misleading obsolete comment
The spinlock handling in this file has changed significantly since this comment was written, and the file_lock_lock is no more. In addition, this overall comment no longer applies. Deleting an entry now requires both locks. Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs')
-rw-r--r--fs/locks.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/fs/locks.c b/fs/locks.c
index 6138a9bcd924..11a4d698aba8 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -202,10 +202,6 @@ static DEFINE_HASHTABLE(blocked_hash, BLOCKED_HASH_BITS);
* we often hold the flc_lock as well. In certain cases, when reading the fields
* protected by this lock, we can skip acquiring it iff we already hold the
* flc_lock.
- *
- * In particular, adding an entry to the fl_block list requires that you hold
- * both the flc_lock and the blocked_lock_lock (acquired in that order).
- * Deleting an entry from the list however only requires the file_lock_lock.
*/
static DEFINE_SPINLOCK(blocked_lock_lock);