On 11/5/26 22:30, Lorenzo Stoakes (ARM) wrote: > Continue the conversion of legacy vm_flags_t flags to the new vma_flags_t > bitmap type. > > Do some more core mm conversion (we really should be the first to > completely move to the new scheme :), but also update some mm-adjacent and > otherwise straightforward cases - /proc/$pid/maps and friends, the coredump > VMA dump size logic, uprobes, perf and LSM mmap/mprotect hooks. > > This series only makes strictly mechanical changes to keep things gentle > during this very busy cycle. > > No functional change intended. > > Build tested on x86-64 (allmodconfig, each patch individually), i386, > arm64, riscv nommu and ppc64le. > > Signed-off-by: Lorenzo Stoakes (ARM) <[email protected]> > --- > Lorenzo Stoakes (ARM) (13): > mm/gup: convert GUP code to use vma_flags_t > mm/filemap: convert fault and readahead logic to use vma_flags_t > mm/rmap: convert remaining VMA flag tests to use vma_flags_t > mm/migrate: convert VMA flag tests to use vma_flags_t > mm: convert THP VMA flag tests to use vma_flags_t > mm/ksm: convert VMA flag tests to use vma_flags_t > mm/madvise: convert madvise_vma_behavior() to use vma_flags_t > mm: convert miscellaneous VMA flag tests to use vma_flags_t > fs/proc/task_mmu: convert VMA flag tests to use vma_flags_t > fs/coredump: convert vma_dump_size() to use vma_flags_t > uprobes: convert VMA flag tests to use vma_flags_t > perf: convert VMA flag tests to use vma_flags_t > security: convert VMA flag tests to use vma_flags_t >
I agree that this should be picked separately. For example, I will pick everything that falls into my realm to reduce conflicts. Ideally, patches really only touch one component. [PATCH 07/13] mm/madvise: convert madvise_vma_behavior() to use vma_flags_t is all over the place :) -- Cheers, David
