Re: [PATCH v5 33/38] mm: eliminate VMA_SPECIAL_FLAGS usage when hugetlb explicitly tested
flat view
From: sashiko-bot@kernel.org
Date: 2026-10-09 18:47:55
Also in:
bpf, dri-devel, kvm, kvmarm, linux-perf-users, linux-rdma, linux-s390, linux-scsi, linux-usb, selinux
It is now an invariant that VMA_IO_BIT is not set by mm-managed mappings, so each existing VMA_SPECIAL_FLAGS test need only test for VMA_DONTEXPAND_BIT, VMA_PFNMAP_BIT and VMA_MIXEDMAP_BIT. This is precisely a test for a fixed or non-mm-managed mapping. Update a number of callsites which already explicitly handle hugetlb mappings. vma_supports_mlock() and ksm_compatible() also explicitly bail on droppable mappings - excluding non-mm-managed, fixed or droppable mappings is exactly what vma_is_mm_backed() tests for, so in these cases use this predicate. should_skip_vma() tests for locked, fixed or non-mm-managed memory (having already excluded hugetlb mappings) so simply test for those there. No functional change intended. Reviewed-by: Zi Yan <ziy@nvidia.com> Signed-off-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review · https://sashiko.dev/#/patchset/20261009-b4-mmap-prepare-vma-flag-sanify-v5-0-923b70125b1e@kernel.org?part=33