linux-kernel - Re: [PATCH v2 0/2] x86/mm: support memory-failure on 32-bits with SPARSEMEM

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: <20251105024523.14300-1-xieyuanbin1@huawei.com>
Date: Wed, 5 Nov 2025 10:45:23 +0800
From: Xie Yuanbin <xieyuanbin1@...wei.com>
To: <dave.hansen@...el.com>, <david@...nel.org>
CC: <Liam.Howlett@...cle.com>, <akpm@...ux-foundation.org>, <bp@...en8.de>,
	<dave.hansen@...ux.intel.com>, <david@...hat.com>, <hpa@...or.com>,
	<liaohua4@...wei.com>, <lilinjie8@...wei.com>, <linmiaohe@...wei.com>,
	<linux-edac@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linux-mm@...ck.org>, <lorenzo.stoakes@...cle.com>, <luto@...nel.org>,
	<mhocko@...e.com>, <mingo@...hat.com>, <nao.horiguchi@...il.com>,
	<peterz@...radead.org>, <rppt@...nel.org>, <surenb@...gle.com>,
	<tglx@...utronix.de>, <tony.luck@...el.com>, <vbabka@...e.cz>,
	<will@...nel.org>, <x86@...nel.org>, <xieyuanbin1@...wei.com>
Subject: Re: [PATCH v2 0/2] x86/mm: support memory-failure on 32-bits with SPARSEMEM

On Tue, 4 Nov 2025 06:26:58 -0800, Dave Hansen wrote:
> Which LLM generated that for you, btw?

I wrote this myself; LLM just helped me with the translation. My English
isn't very good, so I apologize for any mistakes.

> I wanted to know _specifically_ what kind of hardware or 32-bit
> environment you wanted to support with this series, though.

I think I have explained it clearly enough in this email:
Link: https://lore.kernel.org/20251104133254.145660-1-xieyuanbin1@huawei.com

In simple terms, it refers to some old existing equipment and some
embedded devices. More specifically, it includes some routers, switches,
and similar devices. From what I know, there is no VM environment that
using it.
If you are asking about a specific CPU chip model, I'm sorry, but I may
not be able to provide that information for you.

Btw, why do you only ask about which x86_32 devices use memory-failure,
but not which x86_32 devices use sparsemem? This patch just allows both
to coexist, and perhaps both are important?

Thanks!

Xie Yuanbin