[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241118183514.112db8b9@kernel.org>
Date: Mon, 18 Nov 2024 18:35:14 -0800
From: Jakub Kicinski <kuba@...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>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, 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, max@...sevol.com, thepacketgeek@...il.com,
vlad.wing@...il.com, davej@...emonkey.org.uk
Subject: Re: [PATCH net-next 4/4] netconsole: selftest: Validate CPU number
auto-population in userdata
On Wed, 13 Nov 2024 07:10:55 -0800 Breno Leitao wrote:
> + if ! grep -q "cpu=[0-9]\+" "${TMPFILENAME}"; then
> + echo "FAIL: 'cpu=' not found in ${TMPFILENAME}" >&2
> + cat "${TMPFILENAME}" >&2
> + exit "${ksft_fail}"
> + fi
Could we try to do something like pick a 'random' CPU ID from sysfs,
taskset the write / echo, and match that the incoming message has the
expected CPU ID, not just any?
Powered by blists - more mailing lists