Re: [PATCH v2 1/3] vmalloc: add __GFP_SKIP_KASAN support

[David Hildenbrand (Arm)]

>> I think we are doing patch 1 because of patch 2 - so in patch 2, perhaps
>> instead of calling __vmalloc_node we can call __vmalloc_node_range_noprof and
>> shift this "skip vmalloc unpoisoning" functionality into vmalloc flags instead?
> 
> This is exactly how Usama was doing it in v1. I suggested we should just reuse
> the existing flag since it already provides the semantic we want and is less
> confusing than introducing a new flag.
> 
> I know David is keen to do a wider rework and remove/rename/change the semantics
> of __GFP_SKIP_KASAN, but I'm hoping that if we just continue to use the existing
> flag and its semantics for vmalloc then there is no reason why this series can't
> be merged independently of that wider rework.

Independent of how the flag will be called, I think it will have the same
semantics. How we'll implement that internally is a different question.

So I agree that adding __GFP_SKIP_KASAN support here is the right approach for
the time being.

-- 
Cheers,

David