linux-kernel - Re: [PATCH v2 1/1] mm: numa_memblks: Identify the accurate NUMA ID of CFMW

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: <20260205145842.efb90572a902ae4c481e6ef6@linux-foundation.org>
Date: Thu, 5 Feb 2026 14:58:42 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Cui Chao <cuichao1753@...tium.com.cn>
Cc: Gregory Price <gourry@...rry.net>, dan.j.williams@...el.com, Jonathan
 Cameron <Jonathan.Cameron@...wei.com>, Mike Rapoport <rppt@...nel.org>,
 Wang Yinfeng <wangyinfeng@...tium.com.cn>, linux-cxl@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 1/1] mm: numa_memblks: Identify the accurate NUMA ID
 of CFMW

On Mon, 26 Jan 2026 17:06:52 +0800 Cui Chao <cuichao1753@...tium.com.cn> wrote:

> > All that said, this does look harmless, and seems reasonable - but the
> > changelog should reflect what the hardware is doing above.
> This issue was discovered on the QEMU platform. I need to apologize for 
> my earlier imprecise statement (claiming it was hardware instead of 
> QEMU). My core point at the time was to emphasize that this is a problem 
> in the general code path when facing this scenario, not a QEMU-specific 
> emulation issue, and therefore it could theoretically affect real 
> hardware as well. I apologize for any confusion this may have caused.

This patch doesn't sounds very urgent.  Perhaps we should do a v3 with
updated changelog and handle that in the next -rc cycle?