vmap_page_range() does flushing and it has instrumented KMSAN inside. We should follow same semantic. Also it uses ioremap_max_page_shift as maximum page shift policy.
Not quite sure if vmap() should follow ioremap()’s ioremap_max_page_shift. If needed, it shouldn’t be difficult to do so.
I have a version queued for testing (Xueyuan is working hard on it). Meanwhile, if you have any comments, please feel free to share.
diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 57eae99d9909..8d449e78a07a 100644
Hi Uladzislau, David,
As explained there [1], this standalone patch is withdrawn, as I have moved to a series that addresses a broader set of issues. Sorry for any confusion this may have caused.
[1] https://lore.kernel.org/all/CAGsJ_4wCBeVfyFraj_dRdsUrSNqDG5a8SO9C3=PFRSt04dR...
Best Regards Barry