From: Shakeel Butt <shakeel.butt@linux.dev>
To: SeongJae Park <sj@kernel.org>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 1/4] mm/madvise: split out mmap locking operations for madvise()
Date: Wed, 29 Jan 2025 11:18:24 -0800 [thread overview]
Message-ID: <oxfyhyykypb7mzpqlwq3fuy2hyvt37ykrjvcsndbljgzm6eysa@ieyq7xykk364> (raw)
In-Reply-To: <20250117013058.1843-2-sj@kernel.org>
On Thu, Jan 16, 2025 at 05:30:55PM -0800, SeongJae Park wrote:
> Split out the madvise behavior-dependent mmap_lock operations from
> do_madvise(), for easier reuse of the logic in an upcoming change.
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
next prev parent reply other threads:[~2025-01-29 19:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 1:30 [RFC PATCH v2 0/4] mm/madvise: remove redundant mmap_lock operations from process_madvise() SeongJae Park
2025-01-17 1:30 ` [RFC PATCH v2 1/4] mm/madvise: split out mmap locking operations for madvise() SeongJae Park
2025-01-29 19:18 ` Shakeel Butt [this message]
2025-01-31 15:58 ` Lorenzo Stoakes
2025-01-31 17:33 ` Davidlohr Bueso
2025-01-17 1:30 ` [RFC PATCH v2 2/4] mm/madvise: split out madvise input validity check SeongJae Park
2025-01-29 19:18 ` Shakeel Butt
2025-01-31 16:01 ` Lorenzo Stoakes
2025-01-31 19:19 ` Davidlohr Bueso
2025-01-17 1:30 ` [RFC PATCH v2 3/4] mm/madvise: split out madvise() behavior execution SeongJae Park
2025-01-29 19:19 ` Shakeel Butt
2025-01-31 16:10 ` Lorenzo Stoakes
2025-01-17 1:30 ` [RFC PATCH v2 4/4] mm/madvise: remove redundant mmap_lock operations from process_madvise() SeongJae Park
2025-01-29 19:20 ` Shakeel Butt
2025-01-31 16:53 ` Lorenzo Stoakes
2025-01-31 17:31 ` Davidlohr Bueso
2025-01-31 17:47 ` Liam R. Howlett
2025-01-31 17:51 ` Lorenzo Stoakes
2025-01-31 17:58 ` Davidlohr Bueso
2025-02-04 19:53 ` SeongJae Park
2025-02-06 6:28 ` SeongJae Park
2025-05-17 19:28 ` Lorenzo Stoakes
2025-05-19 18:25 ` SeongJae Park
2025-01-31 19:17 ` Shakeel Butt
2025-02-04 18:56 ` SeongJae Park
2025-01-29 19:22 ` [RFC PATCH v2 0/4] " Shakeel Butt
2025-01-29 21:09 ` SeongJae Park
2025-01-31 16:04 ` Liam R. Howlett
2025-01-31 16:30 ` SeongJae Park
2025-01-31 16:55 ` Lorenzo Stoakes
2025-01-31 17:53 ` Lorenzo Stoakes
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=oxfyhyykypb7mzpqlwq3fuy2hyvt37ykrjvcsndbljgzm6eysa@ieyq7xykk364 \
--to=shakeel.butt@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
/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