Re: [PATCH] mm/memory-failure: fix folio refcount leak and min_order_for_split() locking

[Tal Zussman]

On 10/30/26 10:42 AM, David Hildenbrand (Arm) wrote:
> On 10/30/26 11:50, Tal Zussman wrote:
>> On Thu, Aug 06, 2026 at 01:14:38PM +0200, David Hildenbrand (Arm) wrote:
>>> hwpoison code can end up calling min_order_for_split() without holding
>>> the folio lock. There isn't really something that would prevent
>>> concurrent folio split. Consequently folio->mapping can get set to
>>> NULL after checking for "!folio->mapping", and if the compiler
>>> reloads folio->mapping, mapping_min_folio_order() would try to
>>> dereference NULL.
>> 
>> Hi David,
>> 
>> Did this patch ever make it in?
> 
> If you ask this way ... I guess not? :D
> 

:)

> I can see if it still applies and resend + apply.

That would be great, thanks!