From: Andrew Morton <akpm@linux-foundation.org>
To: Stanislav Kinsburskii <skinsburskii@gmail.com>
Cc: Liam.Howlett@oracle.com, david@kernel.org, jgg@ziepe.ca,
corbet@lwn.net, leon@kernel.org, ljs@kernel.org, mhocko@suse.com,
rppt@kernel.org, shuah@kernel.org, skhan@linuxfoundation.org,
surenb@google.com, vbabka@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 0/3] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings
Date: Tue, 30 Jun 2026 13:19:15 -0700 [thread overview]
Message-ID: <20260630131915.a7a479fc92ad0b86bfc68173@linux-foundation.org> (raw)
In-Reply-To: <178283277041.183052.6873574850714079228.stgit@skinsburskii>
On Tue, 30 Jun 2026 08:21:21 -0700 Stanislav Kinsburskii <skinsburskii@gmail.com> wrote:
> This series extends the HMM framework to support userfaultfd-backed memory
> by allowing the mmap read lock to be dropped during hmm_range_fault().
Cool.
AI review might have found some issues:
https://sashiko.dev/#/patchset/178283277041.183052.6873574850714079228.stgit@skinsburskii
One of these is pre-existing so please take a look, see if there's
something you feel should be done about it.
As the series is presently unreviewed, I'll await that review feedback
and/or v5, thanks.
prev parent reply other threads:[~2026-06-30 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 15:21 [PATCH v4 0/3] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Stanislav Kinsburskii
2026-06-30 15:21 ` [PATCH v4 1/3] mm/hmm: move page fault handling out of walk callbacks Stanislav Kinsburskii
2026-06-30 15:21 ` [PATCH v4 2/3] mm/hmm: add hmm_range_fault_unlockable() for mmap lock-drop support Stanislav Kinsburskii
2026-06-30 15:21 ` [PATCH v4 3/3] selftests/mm: add userfaultfd test for HMM unlockable path Stanislav Kinsburskii
2026-06-30 20:19 ` Andrew Morton [this message]
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=20260630131915.a7a479fc92ad0b86bfc68173@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skinsburskii@gmail.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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