Re: (subset) [PATCH 0/3] mm/memory: fix handling of PTE markers in insert_page_into_pte_locked()

From: David Hildenbrand

Date: Wed Nov 18 2026 - 09:56:32 EST


On Tue, 17 Nov 2026 17:58:31 +0200, Mike Rapoport (Microsoft) wrote:
> Jingyi reported that a uffd-wp marker in a DAX mapping causes endless
> refaults on reads and SIGBUS on writes [1].
>
> The root cause is that insert_page_into_pte_locked() treats every PTE that
> is not none as a present mapping. Besides uffd-wp markers, this also
> affects guard markers that MADV_GUARD_INSTALL can put into a DAX mapping
> concurrently with a write fault.
>
> [...]

Applied, thanks!

tree: mm/core.git
branch: core-7.5.misc

Applied patches will appear soon in mm-next, followed by linux-next.

Please report any outstanding bugs that were missed during review, so we
can either drop the patch series or decide how to fix it up.

It is encouraged to provide Acked-bys, Reviewed-bys, and Tested-bys even
though the patches have already been applied. If possible, patch trailers
will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. Further, this is not a guarantee that the
patches will go upstream. If in doubt, please check the listed branch.

[3/3] mm/memory: don't upgrade non-present PTEs in insert_page_into_pte_locked()
https://git.kernel.org/mm/core/c/3fa9917a

--
Cheers,

David