From: Paolo Abeni <pabeni@redhat.com>
To: Bobby Eshleman <bobbyeshleman@gmail.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Shuah Khan <shuah@kernel.org>
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Bobby Eshleman <bobbyeshleman@meta.com>
Subject: Re: [PATCH net-next 1/2] selftests/vsock: fix vmtest.sh for read-only nested VM runners
Date: Tue, 17 Mar 2026 15:46:35 +0100 [thread overview]
Message-ID: <302d1a45-dd5d-4d50-a99c-ce73de196d0c@redhat.com> (raw)
In-Reply-To: <20260313-vsock-vmtest-nested-fixes-v1-1-d0e6274c3193@meta.com>
On 3/14/26 1:00 AM, Bobby Eshleman wrote:
> tools/testing/selftests/vsock/vmtest.sh | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/vsock/vmtest.sh b/tools/testing/selftests/vsock/vmtest.sh
> index 86e338886b33..c2cfcdf05d99 100755
> --- a/tools/testing/selftests/vsock/vmtest.sh
> +++ b/tools/testing/selftests/vsock/vmtest.sh
> @@ -42,6 +42,8 @@ readonly KERNEL_CMDLINE="\
> virtme.ssh virtme_ssh_channel=tcp virtme_ssh_user=$USER \
> "
> readonly LOG=$(mktemp /tmp/vsock_vmtest_XXXX.log)
> +readonly TEST_HOME=$(mktemp -d /tmp/vmtest_home_XXXX)
shellcheck complains:
In vmtest.sh line 45:
readonly TEST_HOME=$(mktemp -d /tmp/vmtest_home_XXXX)
^-------^ SC2155 (warning): Declare and assign separately to
avoid masking return values.
> @@ -451,11 +464,14 @@ vm_start() {
> --run \
> ${kernel_opt} \
> ${verbose_opt} \
> + --rwdir=/root=${TEST_HOME} \
And here, too:
In vmtest.sh line 467:
--rwdir=/root=${TEST_HOME} \
^----------^ SC2086 (info): Double quote
to prevent globbing and word splitting.
Did you mean:
--rwdir=/root="${TEST_HOME}" \
The first occurrence could possibly be explicitly silenced explicitly,
but it's probably better to really address the latter.
/P
next prev parent reply other threads:[~2026-03-17 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 0:00 [PATCH net-next 0/2] selftests/vsock: support nested VM runner for vmtest.sh Bobby Eshleman
2026-03-14 0:00 ` [PATCH net-next 1/2] selftests/vsock: fix vmtest.sh for read-only nested VM runners Bobby Eshleman
2026-03-17 14:46 ` Paolo Abeni [this message]
2026-03-17 21:41 ` Bobby Eshleman
2026-03-14 0:00 ` [PATCH net-next 2/2] selftests/vsock: fix vsock_test path shadowing in nested VMs Bobby Eshleman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=302d1a45-dd5d-4d50-a99c-ce73de196d0c@redhat.com \
--to=pabeni@redhat.com \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox