Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit da33a871 authored by Jeff Layton's avatar Jeff Layton
Browse files

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: default avatarJeff Layton <jlayton@kernel.org>
parent 96c25b77

fs/locks.c

+0 −4
Original line number Original line Diff line number Diff line
@@ -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

 * 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

 * protected by this lock, we can skip acquiring it iff we already hold the

 * flc_lock.

 * 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);

static DEFINE_SPINLOCK(blocked_lock_lock);