From: Jinliang Zheng <alexjlzheng@gmail.com>
Date: Fri, 13 Dec 2024 03:18:20 +0000 (+0800)
Subject: mm: fix outdated incorrect code comments for handle_mm_fault()
X-Git-Tag: microblaze-v6.16~78^2~197
X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=8e6173ccf7b87c1f855e1ad3d94fd50c51d1f46b;p=linux-2.6-microblaze.git

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>
---

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().