diff mbox series

[v2] mm: fix outdated incorrect code comments for handle_mm_fault()

Message ID 20241214030050.1702776-1-alexjlzheng@tencent.com (mailing list archive)
State New
Headers show
Series [v2] mm: fix outdated incorrect code comments for handle_mm_fault() | expand

Commit Message

Jinliang Zheng Dec. 14, 2024, 3 a.m. UTC 
Signed-off-by: Jinliang Zheng <alexjlzheng@tencent.com>
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
changelog:
- v2: lower case mmap_Lock to mmap_lock
- v1: https://lore.kernel.org/linux-mm/20241213031820.778342-1-alexjlzheng@tencent.com/#r
---
 mm/memory.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff mbox series

Patch

diff --git a/mm/memory.c b/mm/memory.c
index d9af83dd86bb..9d64e02341f8 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -6159,7 +6159,8 @@  static vm_fault_t sanitize_fault_flags(struct vm_area_struct *vma,
 }
 
 /*
- * By the time we get here, we already hold the mm semaphore
+ * By the time we get here, we already hold either the VMA lock or the
+ * mmap_lock (FAULT_FLAG_VMA_LOCK tells you which).
  *
  * The mmap_lock may have been released depending on flags and our
  * return value.  See filemap_fault() and __folio_lock_or_retry().