netdev - Re: [PATCH RFC net-next v3 7/8] netconsole: selftest: test for sysdata CPU

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: <20250130103859.GK113107@kernel.org>
Date: Thu, 30 Jan 2025 10:38:59 +0000
From: Simon Horman <horms@...nel.org>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Jonathan Corbet <corbet@....net>, Shuah Khan <shuah@...nel.org>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org,
	rdunlap@...radead.org, kernel-team@...a.com
Subject: Re: [PATCH RFC net-next v3 7/8] netconsole: selftest: test for
 sysdata CPU

On Fri, Jan 24, 2025 at 07:16:46AM -0800, Breno Leitao wrote:
> Add a new selftest to verify that the netconsole module correctly
> handles CPU runtime data in sysdata. The test validates three scenarios:
> 
> 1. Basic CPU sysdata functionality - verifies that cpu=X is appended to
>    messages
> 2. CPU sysdata with userdata - ensures CPU data works alongside userdata
> 3. Disabled CPU sysdata - confirms no CPU data is included when disabled
> 
> The test uses taskset to control which CPU sends messages and verifies
> the reported CPU matches the one used. This helps ensure that netconsole
> accurately tracks and reports the originating CPU of messages.
> 
> Signed-off-by: Breno Leitao <leitao@...ian.org>

Reviewed-by: Simon Horman <horms@...nel.org>