From: Barry Song <21cnbao@gmail.com>
To: lorenzo.stoakes@oracle.com, akpm@linux-foundation.org
Cc: 21cnbao@gmail.com, Liam.Howlett@oracle.com, david@redhat.com,
jannh@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lokeshgidra@google.com, surenb@google.com,
v-songbaohua@oppo.com, vbabka@suse.cz,
zhengqi.arch@bytedance.com, zhengtangquan@oppo.com
Subject: Re: [PATCH v3] mm: use per_vma lock for MADV_DONTNEED
Date: Sat, 7 Jun 2025 21:33:44 +1200 [thread overview]
Message-ID: <20250607093344.15699-1-21cnbao@gmail.com> (raw)
In-Reply-To: <69846ab3-de03-48bc-acd7-60e8a458c263@lucifer.local>
>
> Whoops, I should add R-b only applies with the fix-patch proposed in [0].
>
> [0]: https://lore.kernel.org/all/CAGsJ_4x1RbQ+GKKc1rrTaNA8Xd+W8K-Zu6-kwVYNKzB0OWiowQ@mail.gmail.com/
>
> Barry - Probably worth respinning a v4 to pick that up to make things
> clear, you can propagate my tag with that.
Sure. It's a small, non-functional change:
diff --git a/mm/madvise.c b/mm/madvise.c
index a94e6a7ee387..8382614b71d1 100644
--- a/mm/madvise.c
+++ b/mm/madvise.c
@@ -1534,8 +1534,7 @@ int madvise_walk_vmas(struct mm_struct *mm, unsigned long start,
if (madv_behavior && madv_behavior->lock_mode == MADVISE_VMA_READ_LOCK) {
vma = try_vma_read_lock(mm, madv_behavior, start, end);
if (vma) {
- error = madvise_vma_behavior(vma, &prev, start, end,
- madv_behavior);
+ error = visit(vma, &prev, start, end, arg);
vma_end_read(vma);
return error;
}
>
> Cheers, Lorenzo
Thanks
Barry
next prev parent reply other threads:[~2025-06-07 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 0:46 Barry Song
2025-06-07 4:04 ` Matthew Wilcox
2025-06-07 4:53 ` Barry Song
2025-06-07 7:24 ` Lorenzo Stoakes
2025-06-07 6:36 ` Lorenzo Stoakes
2025-06-07 7:22 ` Lorenzo Stoakes
2025-06-07 7:26 ` Lorenzo Stoakes
2025-06-07 9:33 ` Barry Song [this message]
2025-06-07 10:30 ` Barry Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250607093344.15699-1-21cnbao@gmail.com \
--to=21cnbao@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=vbabka@suse.cz \
--cc=zhengqi.arch@bytedance.com \
--cc=zhengtangquan@oppo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox