On Thu, Feb 15, 2024 at 12:50:55PM -0800, Alexei Starovoitov wrote: > So, since apply_to_page_range() is available to the kernel > (xen, gpu, kasan, etc) then I see no reason why > vmap_pages_range() shouldn't be available as well, since: In case it wasn't clear before: apply_to_page_range is a bad API to be exported. We've been working on removing it but it stalled. Exposing something that allows a module to change arbitrary page table bits is not a good idea. Please take a step back and think of how to expose a vmalloc like allocation that grows only when used as a proper abstraction. I could actually think of various other uses for it.
