netdev - Re: [PATCH net-next 05/12] selftests/vsock: do not unconditionally die if qemu fails

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: <aQJH0D2BGGo6F_s_@horms.kernel.org>
Date: Wed, 29 Oct 2025 16:58:56 +0000
From: Simon Horman <horms@...nel.org>
To: Bobby Eshleman <bobbyeshleman@...il.com>
Cc: Stefano Garzarella <sgarzare@...hat.com>, Shuah Khan <shuah@...nel.org>,
	Jakub Kicinski <kuba@...nel.org>, virtualization@...ts.linux.dev,
	netdev@...r.kernel.org, linux-kselftest@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Bobby Eshleman <bobbyeshleman@...a.com>
Subject: Re: [PATCH net-next 05/12] selftests/vsock: do not unconditionally
 die if qemu fails

On Wed, Oct 22, 2025 at 06:00:09PM -0700, Bobby Eshleman wrote:
> From: Bobby Eshleman <bobbyeshleman@...a.com>
> 
> If QEMU fails to boot, then set the returncode (via timeout) instead of
> unconditionally dying. This is in preparation for tests that expect QEMU
> to fail to boot. In that case, we just want to know if the boot failed
> or not so we can test the pass/fail criteria, and continue executing the
> next test.
> 
> Signed-off-by: Bobby Eshleman <bobbyeshleman@...a.com>

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