Re: [PATCH v5 6/9] mm/memory-failure: efi: answer whether a range is poisoned

[David Hildenbrand (Arm)]

On 9/15/26 15:45, sashiko-bot@xxxxxxxxxx wrote:
>> The bitmap an earlier kernel filled in gets in this one through EFI,
>> but nothing reads it back yet.
>>
>> Introduce range_contains_poisoned_memory(), which the page allocator
>> will use to ask about a block before handing it out.
>>
>> Signed-off-by: Breno Leitao <leitao@xxxxxxxxxx>
> 
> Sashiko has reviewed this patch and found no issues. It looks great!
> 

David has reviewed this mail and it annoyed him.

-- 
Cheers,

David