From: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>
To: jgg@ziepe.ca, leon@kernel.org, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] mm/hmm: Add userfaultfd support to fault handling
Date: Thu, 02 Apr 2026 16:37:18 +0000 [thread overview]
Message-ID: <177514781712.83496.13387671641142309152.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net> (raw)
Add support for userfaultfd-enabled VMAs to the HMM framework.
Extract fault handling logic into hmm_handle_mm_fault() to handle both
regular and userfaultfd-backed mappings. The implementation follows
fixup_user_fault() for handling VM_FAULT_RETRY and VM_FAULT_COMPLETED, with
a key difference: instead of retrying or moving forward respectively,
return -EBUSY after reacquiring mmap_read_lock. Since the lock was
released, the VMA could have changed, so defer retry logic to the caller.
This approach is inefficient for userfaultfd-backed VMAs, as HMM can only
populate one page at a time, but keeps the framework simple by avoiding
complex retry logic within HMM itself.
v2: Addressed sashiko review comments
Signed-off-by: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>
---
mm/hmm.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 54 insertions(+), 4 deletions(-)
diff --git a/mm/hmm.c b/mm/hmm.c
index f6c4ddff4bd6..284032c4b2c8 100644
--- a/mm/hmm.c
+++ b/mm/hmm.c
@@ -59,6 +59,53 @@ static int hmm_pfns_fill(unsigned long addr, unsigned long end,
return 0;
}
+static int hmm_handle_mm_fault(struct vm_area_struct *vma,
+ unsigned long addr,
+ unsigned int fault_flags)
+{
+ int ret;
+
+ if (userfaultfd_armed(vma)) {
+ struct mm_struct *mm = vma->vm_mm;
+
+ /*
+ * handle_mm_fault() with FAULT_FLAG_ALLOW_RETRY will
+ * release the mmap lock via mmap_read_unlock() on
+ * VM_FAULT_RETRY or VM_FAULT_COMPLETED.
+ * If the caller holds the lock in write mode, the
+ * mmap_read_unlock() call would corrupt the rwsem state.
+ * Assert that we only hold a read lock here.
+ */
+ lockdep_assert_held_read(&mm->mmap_lock);
+
+ fault_flags |= FAULT_FLAG_ALLOW_RETRY |
+ FAULT_FLAG_USER |
+ FAULT_FLAG_KILLABLE;
+
+ ret = handle_mm_fault(vma, addr, fault_flags, NULL);
+
+ if (ret & VM_FAULT_COMPLETED) {
+ mmap_read_lock(mm);
+ return -EBUSY;
+ }
+
+ if (ret & VM_FAULT_RETRY) {
+ mmap_read_lock(mm);
+ if (fatal_signal_pending(current))
+ return -EINTR;
+ return -EBUSY;
+ }
+
+ if (ret & VM_FAULT_ERROR)
+ return vm_fault_to_errno(ret, 0);
+ } else {
+ ret = handle_mm_fault(vma, addr, fault_flags, NULL);
+ if (ret & VM_FAULT_ERROR)
+ return vm_fault_to_errno(ret, 0);
+ }
+ return 0;
+}
+
/*
* hmm_vma_fault() - fault in a range lacking valid pmd or pte(s)
* @addr: range virtual start address (inclusive)
@@ -86,10 +133,13 @@ static int hmm_vma_fault(unsigned long addr, unsigned long end,
fault_flags |= FAULT_FLAG_WRITE;
}
- for (; addr < end; addr += PAGE_SIZE)
- if (handle_mm_fault(vma, addr, fault_flags, NULL) &
- VM_FAULT_ERROR)
- return -EFAULT;
+ for (; addr < end; addr += PAGE_SIZE) {
+ int ret;
+
+ ret = hmm_handle_mm_fault(vma, addr, fault_flags);
+ if (ret)
+ return ret;
+ }
return -EBUSY;
}
next reply other threads:[~2026-04-02 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 16:37 Stanislav Kinsburskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 22:24 Stanislav Kinsburskii
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=177514781712.83496.13387671641142309152.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net \
--to=skinsburskii@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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