linux-kernel - Re: [PATCH v3 2/4] mm/hugetlb: Refactor unmap_hugepage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <542cf4a3-b1f3-4ca1-82b4-56514f9b86ca@redhat.com>
Date: Mon, 28 Apr 2025 22:50:35 +0200
From: David Hildenbrand <david@...hat.com>
To: nifan.cxl@...il.com, muchun.song@...ux.dev, willy@...radead.org
Cc: mcgrof@...nel.org, a.manzanares@...sung.com, dave@...olabs.net,
 akpm@...ux-foundation.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
 Fan Ni <fan.ni@...sung.com>, Sidhartha Kumar <sidhartha.kumar@...cle.com>
Subject: Re: [PATCH v3 2/4] mm/hugetlb: Refactor unmap_hugepage_range() to
 take folio instead of page

On 28.04.25 19:11, nifan.cxl@...il.com wrote:
> From: Fan Ni <fan.ni@...sung.com>
> 
> The function unmap_hugepage_range() has two kinds of users:
> 1) unmap_ref_private(), which passes in the head page of a folio.  Since
>     unmap_ref_private() already takes folio and there are no other uses
>     of the folio struct in the function, it is natural for
>     unmap_hugepage_range() to take folio also.
> 2) All other uses, which pass in NULL pointer.
> 
> In both cases, we can pass in folio. Refactor unmap_hugepage_range() to
> take folio.
> 
> Signed-off-by: Fan Ni <fan.ni@...sung.com>
> Reviewed-by: Muchun Song <muchun.song@...ux.dev>
> Reviewed-by: Sidhartha Kumar <sidhartha.kumar@...cle.com>
> ---


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


-- 
Cheers,

David / dhildenb