Re: [PATCH 1/5] mm,hugetlb: Change mechanism to detect a COW on private mapping

[David Hildenbrand <david@redhat.com>]

On 12.06.25 15:46, Oscar Salvador wrote:
> hugetlb_wp() checks whether the process is trying to COW on a private mapping
> in order to know whether the reservation for that address was already consumed
> or not.
> If it was consumed and we are the ownner of the mapping, the folio will have to
> be unmapped from the other processes.
> 
> Currently, that check is done by looking up the folio in the pagecache and
> compare it to the folio which is mapped in our pagetables.
> If it differs, it means we already mapped it privately before, consuming a
> reservation on the way.
> All we are interested in is whether the mapped folio is anonymous, so we can
> simplify and check for that instead.
> 
> Also, we transition from a trylock to a folio_lock, since the former was only
> needed when hugetlb_fault() had to lock both folios, in order to avoid deadlock.
> 
> Closes: https://lore.kernel.org/lkml/20250513093448.592150-1-gavinguo@igalia.com/

If there is a Closes: there should probably be a Fixes: and a Reported-by:

> Signed-off-by: Oscar Salvador <osalvador@suse.de>
> Suggested-by: Peter Xu <peterx@redhat.com>
> ---

Nothing jumped at me, we'll learn if we missed anything soon I guess :)

Acked-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb