On Wed, Dec 18, 2024 at 11:14 PM Michal Hocko <mhocko@xxxxxxxx> wrote: > > > As I mentioned in giant v2 thread I'm not touching kasan/kmsan > > in this patch set, since it needs its own eyes > > from experts in those bits, > > but when it happens gfp & __GFP_TRYLOCK would be the way > > to adjust whatever is necessary in kasan/kmsan internals. > > > > As Shakeel mentioned, currently kmsan_alloc_page() is gutted, > > since I'm using __GFP_ZERO unconditionally here. > > We don't even get to kmsan_in_runtime() check. > > I have missed that part! That means that you can drop kmsan_alloc_page > altogether no? I think it's still necessary. kmsan_alloc_page() still needs to do the zero-ing.
