From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,zokeefe@google.com,ziy@nvidia.com,shy828301@gmail.com,ryan.roberts@arm.com,ljs@kernel.org,liam@infradead.org,lance.yang@linux.dev,kas@kernel.org,hughd@google.com,dev.jain@arm.com,david@kernel.org,baolin.wang@linux.alibaba.com,baohua@kernel.org,jthoughton@google.com,akpm@linux-foundation.org
Subject: [to-be-updated] mm-khugepaged-never-install-pmds-in-uffd-minor-registered-vmas.patch removed from -mm tree
Date: Wed, 16 Sep 2026 22:37:56 -0700 [thread overview]
Message-ID: <20260917053757.4FB7C1F000FF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/khugepaged: never install PMDs in uffd-minor-registered VMAs
has been removed from the -mm tree. Its filename was
mm-khugepaged-never-install-pmds-in-uffd-minor-registered-vmas.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: James Houghton <jthoughton@google.com>
Subject: mm/khugepaged: never install PMDs in uffd-minor-registered VMAs
Date: Thu, 10 Sep 2026 02:34:10 +0000
Userfaultfd minor faults provides userspace with the ability to manually
install PTEs with UFFDIO_CONTINUE. Right now, MADV_COLLAPSE can map holes
in the VMA when a naturally-aligned THP is present. This is not true for
khugepaged collapse: the PTEs will be retracted, but a PMD will not be
installed.
When MADV_COLLAPSE installs a PMD that mapped holes in the VMA, userspace
is likely to expect UFFDIO_CONTINUE to succeed on the should-be holes.
UFFDIO_CONTINUE will fail and return EEXIST.
This is not inherently a problem, as MADV_COLLAPSE is an explicit
userspace action. But, especially because MADV_COLLAPSE can be invoked by
an external process via process_madvise(), a rogue caller could break a
userfaultfd-minor resolver thread. If khugepaged is later updated to
install PMDs for khugepaged collapsing, that would be a genuine problem.
Userspace cannot generally use MADV_COLLAPSE to resolve userfault minor
faults, as MADV_COLLAPSE will only resolve such faults if a
naturally-aligned THP is present.
The naturally-aligned THP case is the only case where this quirk exists.
Collapsing otherwise requires all PTEs to be present for
userfaultfd-registered VMAs (i.e., max none PTEs is 0), which is correct.
This check is essentially bypassed for naturally-aligned THPs.
khugepaged doesn't actually install PMDs, so it is impossible for the
kernel to silently install mappings that userspace didn't ask for.
Therefore this patch does not need to be backported.
Link: https://lore.kernel.org/20260910023411.514987-1-jthoughton@google.com
Suggested-by: Lance Yang <lance.yang@linux.dev>
Tested-by: Lance Yang <lance.yang@linux.dev>
Signed-off-by: James Houghton <jthoughton@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Barry Song <baohua@kernel.org>
Cc: David Hildenbrand <david@kernel.org>
Cc: Dev Jain <dev.jain@arm.com>
Cc: Hugh Dickins <hughd@google.com>
Cc: Kiryl Shutsemau <kas@kernel.org>
Cc: Lance Yang <lance.yang@linux.dev>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>
Cc: Yang Shi <shy828301@gmail.com>
Cc: Zach O'Keefe <zokeefe@google.com>
Cc: Zi Yan <ziy@nvidia.com>
---
mm/khugepaged.c | 7 +++++++
1 file changed, 7 insertions(+)
--- a/mm/khugepaged.c~mm-khugepaged-never-install-pmds-in-uffd-minor-registered-vmas
+++ a/mm/khugepaged.c
@@ -1834,6 +1834,13 @@ static enum scan_result try_collapse_pte
if (userfaultfd_protected(vma))
return SCAN_PTE_UFFD;
+ /*
+ * Userfaultfd-minor-registered VMAs should not be collapsed, as
+ * userspace is expecting to explicitly install PTEs.
+ */
+ if (userfaultfd_minor(vma))
+ return SCAN_PTE_UFFD;
+
folio = filemap_lock_folio(vma->vm_file->f_mapping,
linear_page_index(vma, haddr));
if (IS_ERR(folio))
_
Patches currently in -mm which might be from jthoughton@google.com are
mm-selftests-adjust-the-madv_collapse-uffd-minor-selftests.patch
reply other threads:[~2026-09-17 5:37 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=20260917053757.4FB7C1F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=jthoughton@google.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=ziy@nvidia.com \
--cc=zokeefe@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.