path: root/fs/kernfs
diff options
authorMichel Lespinasse <>2020-06-08 21:33:54 -0700
committerLinus Torvalds <>2020-06-09 09:39:14 -0700
commitc1e8d7c6a7a682e1405e3e242d32fc377fd196ff (patch)
treeef02402b77990834fbb5bdb1f146fc0393cc8987 /fs/kernfs
parent3e4e28c5a8f01ee4174d639e36ed155ade489a6f (diff)
mmap locking API: convert mmap_sem comments
Convert comments that reference mmap_sem to reference mmap_lock instead. [ fix up linux-next leftovers] [ s/lockaphore/lock/, per Vlastimil] [ more linux-next fixups, per Michel] Signed-off-by: Michel Lespinasse <> Signed-off-by: Andrew Morton <> Reviewed-by: Vlastimil Babka <> Reviewed-by: Daniel Jordan <> Cc: Davidlohr Bueso <> Cc: David Rientjes <> Cc: Hugh Dickins <> Cc: Jason Gunthorpe <> Cc: Jerome Glisse <> Cc: John Hubbard <> Cc: Laurent Dufour <> Cc: Liam Howlett <> Cc: Matthew Wilcox <> Cc: Peter Zijlstra <> Cc: Ying Han <> Link: Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'fs/kernfs')
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/kernfs/file.c b/fs/kernfs/file.c
index fd6ddfe4cd94..06b342d8462b 100644
--- a/fs/kernfs/file.c
+++ b/fs/kernfs/file.c
@@ -652,9 +652,9 @@ static int kernfs_fop_open(struct inode *inode, struct file *file)
* The following is done to give a different lockdep key to
* @of->mutex for files which implement mmap. This is a rather
* crude way to avoid false positive lockdep warning around
- * mm->mmap_sem - mmap nests @of->mutex under mm->mmap_sem and
+ * mm->mmap_lock - mmap nests @of->mutex under mm->mmap_lock and
* reading /sys/block/sda/trace/act_mask grabs sr_mutex, under
- * which mm->mmap_sem nests, while holding @of->mutex. As each
+ * which mm->mmap_lock nests, while holding @of->mutex. As each
* open file has a separate mutex, it's okay as long as those don't
* happen on the same file. At this point, we can't easily give
* each file a separate locking class. Let's differentiate on