[PATCH v2 18/23] mm: update vma_supports_mlock() to use new VMA flags
From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
Date: 2026-03-16 13:09:45
Also in:
linux-mips, linux-mm, linux-riscv, linux-s390, linux-um, linuxppc-dev, lkml, loongarch, selinux
Subsystem:
memory management, memory management - core, the rest · Maintainers:
Andrew Morton, David Hildenbrand, Linus Torvalds
We now have the ability to test all of this using the new vma_flags_t approach, so let's do so. Signed-off-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org> --- mm/internal.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mm/internal.h b/mm/internal.h
index 80d8651441a7..708d240b4198 100644
--- a/mm/internal.h
+++ b/mm/internal.h@@ -1252,7 +1252,9 @@ static inline struct file *maybe_unlock_mmap_for_io(struct vm_fault *vmf, static inline bool vma_supports_mlock(const struct vm_area_struct *vma) { - if (vma->vm_flags & (VM_SPECIAL | VM_DROPPABLE)) + if (vma_test_any_mask(vma, VMA_SPECIAL_FLAGS)) + return false; + if (vma_test_single_mask(vma, VMA_DROPPABLE)) return false; if (vma_is_dax(vma) || is_vm_hugetlb_page(vma)) return false;
--
2.53.0