]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
selftests/vsock: avoid false-positives when checking dmesg
authorBobby Eshleman <bobbyeshleman@meta.com>
Wed, 5 Nov 2025 15:59:19 +0000 (07:59 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 13 Nov 2025 20:37:45 +0000 (15:37 -0500)
commit8224cc7b3462708f923caed2d5bcf94103cbea8f
treea71f1b01e4a7b612a01d50b74efff661b7532d1f
parentc6c9c32d738117d3dfeec22feb435fd0bd5c9ce7
selftests/vsock: avoid false-positives when checking dmesg

[ Upstream commit 3534e03e0ec2e00908765549828a69df5ebefb91 ]

Sometimes VMs will have some intermittent dmesg warnings that are
unrelated to vsock. Change the dmesg parsing to filter on strings
containing 'vsock' to avoid false positive failures that are unrelated
to vsock. The downside is that it is possible for some vsock related
warnings to not contain the substring 'vsock', so those will be missed.

Fixes: a4a65c6fe08b ("selftests/vsock: add initial vmtest.sh for vsock")
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: Bobby Eshleman <bobbyeshleman@meta.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Link: https://patch.msgid.link/20251105-vsock-vmtest-dmesg-fix-v2-1-1a042a14892c@meta.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
tools/testing/selftests/vsock/vmtest.sh