From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>, Peter Xu <peterx@redhat.com>,
Muhammad Usama Anjum <usama.anjum@arm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Chris Mason <mason@kernel.org>, Jingyi Sun <1045704958@qq.com>,
"David Hildenbrand (Arm)" <david@kernel.org>
Subject: [PATCH] mm/userfaultfd: reject DAX mappings
Date: Wed, 18 Nov 2026 11:03:00 +0100 [thread overview]
Message-ID: <20261118-dax_uffd-v1-1-d776cca1ae17@kernel.org> (raw)
UFFD_FEATURE_WP_ASYNC made DAX mappings eligible for userfaultfd
write-protection, but the DAX fault paths have never fully supported it.
DAX faults use vmf_insert_mixed() and vmf_insert_mixed_mkwrite(), which
treats any non-empty PTE, including uffd-wp markers, as an existing mapping.
A read fault on an uffd-wp marker therefore returns VM_FAULT_NOPAGE without
replacing the marker, causing the fault to repeat indefinitely.
PAGEMAP_SCAN can also write-protect a DAX PMD, but the huge DAX write-fault
path can make it writable without clearing its uffd-wp bit, breaking async
write tracking.
Device DAX mappings requiring huge-page alignment and cannot serve PTE
faults after UFFDIO_WRITEPROTECT has split their huge mappings.
So let's just disallow DAX mappings in vma_can_userfault() entirely,
making UFFDIO_REGISTER fail with EINVAL.
Fixes: d61ea1cb0095 ("userfaultfd: UFFD_FEATURE_WP_ASYNC")
Reported-by: Chris Mason <mason@kernel.org>
Reported-by: Jingyi Sun <1045704958@qq.com>
Closes: https://lore.kernel.org/all/tencent_1874C71D4177A1624528043E008DB1A5EF05@qq.com
Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
---
mm/userfaultfd.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index 169f681f9849b..6656233d5dcc7 100644
--- a/mm/userfaultfd.c
+++ b/mm/userfaultfd.c
@@ -2131,6 +2131,9 @@ static bool vma_can_userfault(struct vm_area_struct *vma, vm_flags_t vm_flags,
/* Only mm-backed memory can have its faults handled by userspace. */
if (!vma_is_mm_backed(vma))
return false;
+ /* DAX fault handlers do not support uffd-wp. */
+ if (vma_is_dax(vma))
+ return false;
/* Core mm may discard droppable memory at any time. */
if (vma_test_single_mask(vma, VMA_DROPPABLE))
return false;
---
base-commit: fa4ad798f6f681031775266044ba1b0cf3c670bd
change-id: 20261118-dax_uffd-0fb2c6d1c087
--
Cheers,
David
reply other threads:[~2026-11-18 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261118-dax_uffd-v1-1-d776cca1ae17@kernel.org \
--to=david@kernel.org \
--cc=1045704958@qq.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mason@kernel.org \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=usama.anjum@arm.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