Re: [PATCH v6 25/39] mm/vma: enforce that mm-managed mappings may not set VMA_IO_BIT
flat view
From: "David Hildenbrand (Arm)" <david@kernel.org>
Date: 2026-10-13 15:27:04
Also in:
bpf, dri-devel, fuse-devel, kvm, kvm-riscv, kvmarm, linux-arch, linux-doc, linux-fsdevel, linux-mm, linux-perf-users, linux-rdma, linux-riscv, linux-s390, linux-scsi, linux-sound, linux-trace-kernel, linux-usb, linuxppc-dev, lkml, selinux, sparclinux
On 10/13/26 17:05, Lorenzo Stoakes (ARM) wrote:
It makes no sense for a mapping whose contents the kernel does not own to specify that the range is MMIO. Prior to this patch, all in-tree drivers which did so have been updated such that they are marked as not being mm-managed. The check WARNs and fails the mmap for any out-of-tree driver that still sets VMA_IO_BIT without a kernel mapping. Here VMA_PFNMAP_BIT, VMA_MIXEDMAP are tested individually rather than using vma_flags_is_mm_managed(). This is because vma_flags_is_mm_managed() still checks for VMA_IO_BIT. The very next commit in this series removes this, and the check is then converted to use vma_flags_is_mm_managed(). No functional change intended for in-tree code. Reviewed-by: Zi Yan <ziy@nvidia.com> Signed-off-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Acked-by: David Hildenbrand (Arm) <david@kernel.org> -- Cheers, David