linux-kernel - Re: [PATCH v3 2/3] mm: memory-hotplug: check folio ref count first in do_migrate

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: <6625b73d-64e5-01e5-a114-e667a0ea52bb@huawei.com>
Date: Wed, 19 Feb 2025 11:15:17 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: Wupeng Ma <mawupeng1@...wei.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
	<akpm@...ux-foundation.org>, <david@...hat.com>, <osalvador@...e.de>,
	<nao.horiguchi@...il.com>, <mhocko@...e.com>
Subject: Re: [PATCH v3 2/3] mm: memory-hotplug: check folio ref count first in
 do_migrate_range

On 2025/2/17 9:43, Wupeng Ma wrote:
> From: Ma Wupeng <mawupeng1@...wei.com>
> 
> If a folio has an increased reference count, folio_try_get() will acquire
> it, perform necessary operations, and then release it. In the case of a
> poisoned folio without an elevated reference count (which is unlikely for
> memory-failure), folio_try_get() will simply bypass it.
> 
> Therefore, relocate the folio_try_get() function, responsible for checking
> and acquiring this reference count at first.
> 
> Signed-off-by: Ma Wupeng <mawupeng1@...wei.com>

Acked-by: Miaohe Lin <linmiaohe@...wei.com>

Thanks.
.