summaryrefslogtreecommitdiff
path: root/mm/memory.c
diff options
context:
space:
mode:
authorJinliang Zheng <alexjlzheng@gmail.com>2024-12-13 11:18:20 +0800
committerAndrew Morton <akpm@linux-foundation.org>2025-01-25 20:22:18 -0800
commit8e6173ccf7b87c1f855e1ad3d94fd50c51d1f46b (patch)
tree0723f3a69ce60d3af2ec0655a7ba9a8d5a7e94de /mm/memory.c
parentccd582059a132f2bdc3486766ac57c24c465f471 (diff)
mm: fix outdated incorrect code comments for handle_mm_fault()
[akpm@linux-foundation.org: s/mmap_Lock/mmap_lock/, per Liam] Link: https://lkml.kernel.org/r/20241213031820.778342-1-alexjlzheng@tencent.com Signed-off-by: Jinliang Zheng <alexjlzheng@tencent.com> Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/memory.c')
-rw-r--r--mm/memory.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/mm/memory.c b/mm/memory.c
index 2d97a17dd3ba..90bda3de2191 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -6140,7 +6140,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().