Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Shuah Khan <shuah@kernel.org>, Peter Xu <peterx@redhat.com>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Muchun Song <muchun.song@linux.dev>,
	Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH 0/2] mm/userfaultfd: recheck WP registration in the hugetlb UFFDIO_COPY retry
Date: Sat, 31 Oct 2026 11:20:14 +0200	[thread overview]
Message-ID: <auWyzvThW5EAT_XQ@kernel.org> (raw)
In-Reply-To: <20261029221129.89068-1-azpijr@gmail.com>

Hi Jose,

On Thu, Oct 29, 2026 at 11:11:00PM +0100, Jose A. Perez de Azpillaga wrote:
> The urgent fixes made hugetlb_fault() tolerate uffd bits left in VMAs
> that are no longer registered for them, and asked for follow-ups that
> remove the sources [1]. This is one: a hugetlb UFFDIO_COPY_MODE_WP copy
> that has to fault in its source page doesn't recheck the WP registration
> before retrying, so re-registering the range without WP in that window
> leaves a uffd-wp PTE behind.
> 
> Patch 1 adds the check the non-hugetlb retry already gets from
> mfill_get_vma(). Patch 2 adds a uffd-unit-tests case for it, which fails
> on hugetlb without patch 1.
> 
> Question:
> 
> - The non-hugetlb retry compares the whole mfill_retry_state. hugetlb
>   copies into a freshly allocated folio, so only WP seemed to matter
>   there. Mike, would you rather have the full comparison on both paths?

Let's keep things simple and easily backportable :)

Since hugetlb does not leave a folio from the original VMA behind there's
no inconsistency we need to worry about.
 
> The other source 6/10 of [1] mentions, UFFDIO_COPY in MODE_WP racing
> with UFFDIO_UNREGISTER [2], is closed by "mm/userfaultfd: write-lock the
> VMA before waking waiters when unregistering" [3].
> 
> Based on mm-unstable.
> 
> Tested on x86_64 in QEMU.
> 
> [1] https://lore.kernel.org/20261015-urgent_fixes-v1-0-42796911043b@kernel.org
> [2] https://lore.kernel.org/20261015-urgent_fixes-v1-6-42796911043b@kernel.org
> [3] https://lore.kernel.org/20261027-fixes_core-v1-23-6f74bec9a5bb@kernel.org (v1, now 23/47 in v2)
> 
> Jose A. Perez de Azpillaga (2):
>   mm/userfaultfd: recheck WP registration in the hugetlb UFFDIO_COPY
>     retry
>   selftests/mm: add a uffd test for re-registering during UFFDIO_COPY
> 
>  mm/userfaultfd.c                             |   4 +
>  tools/testing/selftests/mm/uffd-unit-tests.c | 105 +++++++++++++++++++
>  2 files changed, 109 insertions(+)
> 
> 
> base-commit: 24d45a1475dd4c671feb1df705f67ef2fc293969
> -- 
> 2.55.0
> 

-- 
Sincerely yours,
Mike.


      parent reply	other threads:[~2026-10-31  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 22:11 [PATCH 0/2] mm/userfaultfd: recheck WP registration in the hugetlb UFFDIO_COPY retry Jose A. Perez de Azpillaga
2026-10-29 22:11 ` [PATCH 1/2] " Jose A. Perez de Azpillaga
2026-10-31  9:24   ` Mike Rapoport
2026-10-31 12:40     ` Jose A. Perez de Azpillaga
2026-10-29 22:11 ` [PATCH 2/2] selftests/mm: add a uffd test for re-registering during UFFDIO_COPY Jose A. Perez de Azpillaga
2026-10-31  9:35   ` Mike Rapoport
2026-10-31 12:44     ` Jose A. Perez de Azpillaga
2026-10-31  9:20 ` Mike Rapoport [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=auWyzvThW5EAT_XQ@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=azpijr@gmail.com \
    --cc=david@kernel.org \
    --cc=liam@infradead.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=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=peterx@redhat.com \
    --cc=shuah@kernel.org \
    --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