From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Dev Jain <dev.jain@arm.com>, akpm@linux-foundation.org, ljs@kernel.org
Cc: liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, kasong@tencent.com,
qi.zheng@linux.dev, shakeel.butt@linux.dev, baohua@kernel.org,
axelrasmussen@google.com, yuanchu@google.com, weixugc@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
riel@surriel.com, harry@kernel.org, jannh@google.com,
lance.yang@linux.dev, ryan.roberts@arm.com,
anshuman.khandual@arm.com
Subject: Re: [PATCH 3/3] mm/rmap: batch unmap file folios belonging to uffd-wp VMAs
Date: Thu, 16 Jul 2026 11:44:07 +0200 [thread overview]
Message-ID: <62daa36c-7371-4a6e-8b33-901ead69b16d@kernel.org> (raw)
In-Reply-To: <20260715111839.1667914-4-dev.jain@arm.com>
On 7/15/26 13:18, Dev Jain wrote:
> Commit a67fe41e214f ("mm: rmap: support batched unmapping for file large folios")
> extended batched unmapping for file folios. That also required making
> install_uffd_wp_pte_if_needed() support batching, but that was left
> out for the time being, and correctness was maintained by stopping
> batching in case the VMA the folio belongs to is marked uffd-wp.
>
> Now that we have a batched version called cond_install_uffd_wp_ptes,
> simply call that. folio_unmap_pte_batch() ensures that the original state
> of the ptes is either all uffd or all non-uffd, so we maintain
> correctness.
>
> If uffd-wp bit is there, we have the following transitions of ptes
> after unmapping, for a file folio:
>
> present -> uffd-wp marker
>
> We must ensure that these ptes are not reprocessed by the while loop -
> if the batch length is less than the number of pages in the folio, then
> we must skip over this batch.
>
> The page_vma_mapped_walk API ensures this - check_pte() will return true
> only if any of [pvmw->pfn, pvmw->pfn + nr_pages) is mapped by the pte.
> There is no pfn underlying a uffd-wp marker pte, so check_pte returns
> false and we keep skipping until we hit a present entry, which is where
> we want to batch from next.
>
> Note that for the uffd-rwp case, we already do not make a uffd marker in
> cond_install_uffd_wp_ptes.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> Dropped David's ACK due to the uffd-rwp changes.
>
> mm/rmap.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 2f938d0ac6953..ac88673600fa0 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1965,9 +1965,6 @@ static inline unsigned int folio_unmap_pte_batch(struct folio *folio,
> if (pte_unused(pte))
> return 1;
>
> - if (userfaultfd_protected(vma))
> - return 1;
> -
> /*
> * If unmap fails, we need to restore the ptes. To avoid accidentally
> * upgrading write permissions for ptes that were not originally
> @@ -2345,7 +2342,8 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
> * we may want to replace a none pte with a marker pte if
> * it's file-backed, so we don't lose the tracking info.
> */
> - cond_install_uffd_wp_ptes(vma, address, pvmw.pte, pteval, 1);
> + cond_install_uffd_wp_ptes(vma, address, pvmw.pte, pteval,
> + nr_pages);
>
> /* Update high watermark before we lower rss */
> update_hiwater_rss(mm);
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-07-16 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:18 [PATCH 0/3] Batch unmap of uffd-wp file folios Dev Jain
2026-07-15 11:18 ` [PATCH 1/3] mm/memory: move pte_install_uffd_wp_if_needed() into memory.c Dev Jain
2026-07-16 9:35 ` David Hildenbrand (Arm)
2026-07-16 10:06 ` Dev Jain
2026-07-15 11:18 ` [PATCH 2/3] mm/memory: batch set uffd-wp markers during zapping Dev Jain
2026-07-16 9:41 ` David Hildenbrand (Arm)
2026-07-16 10:08 ` Dev Jain
2026-07-15 11:18 ` [PATCH 3/3] mm/rmap: batch unmap file folios belonging to uffd-wp VMAs Dev Jain
2026-07-16 9:44 ` David Hildenbrand (Arm) [this message]
2026-07-15 18:58 ` [PATCH 0/3] Batch unmap of uffd-wp file folios Andrew Morton
2026-07-16 4:57 ` Dev Jain
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=62daa36c-7371-4a6e-8b33-901ead69b16d@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=dev.jain@arm.com \
--cc=harry@kernel.org \
--cc=jannh@google.com \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox