linux-kernel - Re: [PATCH v1] mm/vmscan: Account hwpoisoned folios in reclaim statistics

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: <32a0cfdd-3f6e-47af-86f6-248149ae51ae@redhat.com>
Date: Wed, 2 Jul 2025 11:44:19 +0200
From: David Hildenbrand <david@...hat.com>
To: 18810879172@....com, akpm@...ux-foundation.org
Cc: zhengqi.arch@...edance.com, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org, wangxuewen <wangxuewen@...inos.cn>
Subject: Re: [PATCH v1] mm/vmscan: Account hwpoisoned folios in reclaim
 statistics

On 02.07.25 11:34, 18810879172@....com wrote:
> From: wangxuewen <wangxuewen@...inos.cn>
> 
> When encountering a hardware-poisoned folio in shrink_folio_list(),
> we unmap and release the folio but fail to account it in the reclaim
> statistics (sc->nr_reclaimed). This leads to an undercount of
> actually reclaimed pages, potentially causing unnecessary additional
> reclaim pressure.

I'll just note that this kind-of makes sense: the memory is not actually 
reclaimed -- we don't get free memory back. The hwpoisoned page is lost.

-- 
Cheers,

David / dhildenb