I am not familiar with kmsan internals and my main question is whether this specific usecase really needs a dedicated reentrant kmsan_alloc_page rather than rely on gfp flag to be sufficient. Currently kmsan_in_runtime bails out early in some contexts. The associated comment about hooks is not completely clear to me though. Memory allocation down the road is one of those but it is not really clear to me whether this is the only one. -- Michal Hocko SUSE Labs
