linux-kernel - Re: [PATCH v2 2/2] selftests/bpf: Select NUMA_NO

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] [day] [month] [year] [list]

Message-ID: <7c7f3209-4259-44c2-8d13-94caa88e1468@linux.dev>
Date: Fri, 31 Jan 2025 15:21:12 -0800
From: Yonghong Song <yonghong.song@...ux.dev>
To: Saket Kumar Bhaskar <skb99@...ux.ibm.com>, bpf@...r.kernel.org,
 linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: ast@...nel.org, hbathini@...ux.ibm.com, andrii@...nel.org,
 daniel@...earbox.net, davem@...emloft.net, kuba@...nel.org, hawk@...nel.org,
 martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
 john.fastabend@...il.com, kpsingh@...nel.org, sdf@...ichev.me,
 haoluo@...gle.com, jolsa@...nel.org, mykolal@...com, shuah@...nel.org
Subject: Re: [PATCH v2 2/2] selftests/bpf: Select NUMA_NO_NODE to create map




On 1/30/25 11:05 PM, Saket Kumar Bhaskar wrote:
> On powerpc, a CPU does not necessarily originate from NUMA node 0.
> This contrasts with architectures like x86, where CPU 0 is not
> hot-pluggable, making NUMA node 0 a consistently valid node.
> This discrepancy can lead to failures when creating a map on NUMA
> node 0, which is initialized by default, if no CPUs are allocated
> from NUMA node 0.
>
> This patch fixes the issue by setting NUMA_NO_NODE (-1) for map
> creation for this selftest.
>
> Fixes: 96eabe7a40aa ("bpf: Allow selecting numa node during map creation")
> Signed-off-by: Saket Kumar Bhaskar <skb99@...ux.ibm.com>

Acked-by: Yonghong Song <yonghong.song@...ux.dev>