Re: (subset) [PATCH 0/4] mm: fixes for stale TLB entries due to delayed/batched TLB flushes

From: David Hildenbrand

Date: Fri Nov 20 2026 - 04:02:18 EST


On Wed, 18 Nov 2026 10:20:35 +0100, David Hildenbrand (Arm) wrote:
> David, what keeps you up at night? Well, the last 3 nights, TLB flushes.
>
> We have two mechanisms that can delay/batch TLB flushes and cause
> problems:
>
> (A) mmu_gather zap: we can delay TLB flushes until after dropping the
> PT lock, after having zapped PTEs and adjusted the mapcounts.
>
> [...]

Applied, thanks!

tree: mm/core.git
branch: for-next-fixes

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.

[1/4] mm: flush stale TLB entries before installing a CoW'ed folio
https://git.kernel.org/mm/core/c/5e65fb33
[2/4] mm/vmscan: flush deferred writable TLB entries before unlocking the folio
https://git.kernel.org/mm/core/c/15d1795f

--
Cheers,

David