Re: [PATCH 0/2] mm/mempolicy: shared policy limits for tmpfs/shmem/guest_memfd

From: David Hildenbrand

Date: Tue Nov 17 2026 - 16:35:19 EST


On Fri, 13 Nov 2026 22:36:11 +0100, David Hildenbrand (Arm) wrote:
> For some reason we thought it would be a good idea to let users create
> as many shared policy ranges for shmem/tmpfs as they want. And
> guest_memfd inherited that handling.
>
> Fortunately, at least for guest_memfd we know that we shouldn't really
> have more than one shared policy right now in practice.
>
> [...]

Applied, thanks!

tree: mm/core.git
branch: mempolicy-7.5.shared_policy_limit

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/2] mm/mempolicy: merge adjacent shared policy ranges
https://git.kernel.org/mm/core/c/ca9e4df0
[2/2] mm/mempolicy: limit shared policy ranges per inode
https://git.kernel.org/mm/core/c/8d93a9af

--
Cheers,

David