From: Simon Horman <horms@kernel.org>
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
Shuah Khan <shuah@kernel.org>,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Bobby Eshleman <bobbyeshleman@meta.com>
Subject: Re: [PATCH net-next v3 04/11] selftests/vsock: avoid multi-VM pidfile collisions with QEMU
Date: Fri, 7 Nov 2025 15:08:25 +0000 [thread overview]
Message-ID: <aQ4LaUi9wTnEN8KA@horms.kernel.org> (raw)
In-Reply-To: <20251106-vsock-selftests-fixes-and-improvements-v3-4-519372e8a07b@meta.com>
On Thu, Nov 06, 2025 at 04:49:48PM -0800, Bobby Eshleman wrote:
...
> @@ -90,15 +85,19 @@ vm_ssh() {
> }
>
> cleanup() {
> - if [[ -s "${QEMU_PIDFILE}" ]]; then
> - pkill -SIGTERM -F "${QEMU_PIDFILE}" > /dev/null 2>&1
> - fi
> + local pidfile
>
> - # If failure occurred during or before qemu start up, then we need
> - # to clean this up ourselves.
> - if [[ -e "${QEMU_PIDFILE}" ]]; then
> - rm "${QEMU_PIDFILE}"
> - fi
> + for pidfile in "${PIDFILES[@]}"; do
> + if [[ -s "${pidfile}" ]]; then
> + pkill -SIGTERM -F "${pidfile}" > /dev/null 2>&1
> + fi
> +
> + # If failure occurred during or before qemu start up, then we need
> + # to clean this up ourselves.
> + if [[ -e "${pidfile}" ]]; then
> + rm "${pidfile}"
> + fi
> + done
> }
Hi Bobby,
This is completely untested, but it looks to me
like cleanup() could be implemented more succinctly like this.
cleanup() {
terminate_pidfiles "${PIDFILES[@]}"
}
>
> check_args() {
> @@ -188,10 +187,35 @@ handle_build() {
> popd &>/dev/null
> }
>
> +create_pidfile() {
> + local pidfile
> +
> + pidfile=$(mktemp "${PIDFILE_TEMPLATE}")
> + PIDFILES+=("${pidfile}")
> +
> + echo "${pidfile}"
> +}
> +
> +terminate_pidfiles() {
> + local pidfile
> +
> + for pidfile in "$@"; do
> + if [[ -s "${pidfile}" ]]; then
> + pkill -SIGTERM -F "${pidfile}" > /dev/null 2>&1
> + fi
> +
> + if [[ -e "${pidfile}" ]]; then
> + rm -f "${pidfile}"
> + fi
> + done
I think it would be useful to remove $pidfile from $PIDFILES.
This might be easier to implement if PIDFILES was an associative array.
> +}
> +
...
> @@ -498,7 +529,8 @@ handle_build
> echo "1..${#ARGS[@]}"
>
> log_host "Booting up VM"
> -vm_start
> +pidfile="$(create_pidfile)"
> +vm_start "${pidfile}"
> vm_wait_for_ssh
> log_host "VM booted up"
>
> @@ -522,6 +554,8 @@ for arg in "${ARGS[@]}"; do
> cnt_total=$(( cnt_total + 1 ))
> done
>
> +terminate_pidfiles "${pidfile}"
I am assuming that there will be more calls to terminate_pidfiles
in subsequent patch-sets.
Else I think terminate_pidfiles can be removed
and instead we can rely on cleanup().
> +
> echo "SUMMARY: PASS=${cnt_pass} SKIP=${cnt_skip} FAIL=${cnt_fail}"
> echo "Log: ${LOG}"
>
>
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2025-11-07 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 0:49 [PATCH net-next v3 00/11] selftests/vsock: refactor and improve vmtest infrastructure Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 01/11] selftests/vsock: improve logging in vmtest.sh Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 02/11] selftests/vsock: make wait_for_listener() work even if pipefail is on Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 03/11] selftests/vsock: reuse logic for vsock_test through wrapper functions Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 04/11] selftests/vsock: avoid multi-VM pidfile collisions with QEMU Bobby Eshleman
2025-11-07 15:08 ` Simon Horman [this message]
2025-11-07 15:35 ` Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 05/11] selftests/vsock: do not unconditionally die if qemu fails Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 06/11] selftests/vsock: speed up tests by reducing the QEMU pidfile timeout Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 07/11] selftests/vsock: add check_result() for pass/fail counting Bobby Eshleman
2025-11-11 11:52 ` Simon Horman
2025-11-11 21:01 ` Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 08/11] selftests/vsock: add BUILD=0 definition Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 09/11] selftests/vsock: add 1.37 to tested virtme-ng versions Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 10/11] selftests/vsock: add vsock_loopback module loading Bobby Eshleman
2025-11-07 0:49 ` [PATCH net-next v3 11/11] selftests/vsock: disable shellcheck SC2317 and SC2119 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=aQ4LaUi9wTnEN8KA@horms.kernel.org \
--to=horms@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--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;
as well as URLs for NNTP newsgroup(s).