mm-madvise-remove-redundant-mmap_lock-operations-from-process_madvise-fix

update comment, per Lorenzo

Cc: David Hildenbrand <david@redhat.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: Liam R. Howlett <howlett@gmail.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: SeongJae Park <sj@kernel.org>
Cc: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/mm/madvise.c b/mm/madvise.c
index b48da55bea2218ae3706621a13f666ab9e778588..6ecead476a80958b7067bb101504090e976a36e5 100644 (file)
--- a/mm/madvise.c
+++ b/mm/madvise.c
@@ -1804,7 +1804,7 @@ static ssize_t vector_madvise(struct mm_struct *mm, struct iov_iter *iter,
                 * the operation in aggregate, and would be surprising to the
                 * user.
                 *
-                * As we have already dropped locks, it is safe to just loop and
+                * We drop and reacquire locks so it is safe to just loop and
                 * try again. We check for fatal signals in case we need exit
                 * early anyway.
                 */