Re: [PATCH] mm/numa_emulation: use the real node id for leftover nodes

["Lorenzo Stoakes (ARM)" <ljs@kernel.org>]

On Sun, Nov 15, 2026 at 12:47:06AM +0800, shao.mingyin@zte.com.cn wrote:
> From: Shao Mingyin <shao.mingyin@zte.com.cn>
>
> mm/numa_emulation: use the real node id for leftover nodes
>
> After assigning fake nodes, fix_pxm_node_maps() gives the remaining
> physical nodes free slots in the emulated node space. The second
> distance loop in numa_emulation() derives their physical node IDs by
> subtracting max_emu_nid from those slots. The slot assignment does not
> guarantee that this yields the original physical IDs.
>
> For example, with fake nodes 0 and 1 mapped to physical nodes 0 and 1,
> a remaining physical node 2 assigned slot 2 is read as physical node 1.
> The wrong row of the physical distance table is then installed.
>
> Record the physical ID when assigning each remaining node's slot and
> use that mapping in the distance loop. Keep the first loop's fake-node
> distances, and check the physical IDs before indexing the copied table.
>
> Fixes: 63db8170bf34 ("mm/fake-numa: allow later numa node hotplug")
> Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>

NAK.

this is generated by some AI slopper's script, spamming the kernel. The
patches I looked at were wrong/broken, so no to anything from this person.

They've sent 300 mails in under four weeks spanniing: ata, scsi, target,
ufs, nvme/nvmet, ubifs, ublk, zloop, dm, md, mmc, virtio-blk, mfd, gpio,
pwm, spi, PCI, ASoC, ACPI, net, vfs mount, block partitions, and now mm.

and 17 series across 7 subsystems over the past 23 hours.

We need a way to ban emails from people like this...

--
Cheers, Lorenzo