From: Sean Christopherson <seanjc@google.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, Anup Patel <anup@brainfault.org>,
Oliver Upton <oliver.upton@linux.dev>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
kernel@collabora.com, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests: kvm: replace exit() with ksft_exit_fail_msg()
Date: Wed, 12 Jun 2024 12:01:27 -0700 [thread overview]
Message-ID: <Zmnwhx0Y0qh0x03J@google.com> (raw)
In-Reply-To: <20240612104500.425012-2-usama.anjum@collabora.com>
On Wed, Jun 12, 2024, Muhammad Usama Anjum wrote:
> The KSFT_FAIL, exit code must be used instead of exit(254).
This needs more justification. KVM selftests have worked just fine for 6+ years
using exit(254), so stating they "must" use KSFT_FAIL is obviously not true.
I'm not personally opposed to switching to KSFT_FAIL, but it is a potentially
breaking change. E.g. some of Google's internal test infrastructure explicitly
relies on the exit code being 254. I don't _think_ that infrastructure interacts
with KVM selftests, nor do I think that forcing upstream KVM selftests to sacrifice
TAP compliance just to play nice with someone's crusty test infrastructure is a
good tradeoff, but this and all of the TAP compliance work needs to be done with
more thought and care.
> The 254 code here seems like anciant relic.
As above, AFAICT it comes from Google's internal test infrastructure (KVM selftests
came from Google).
> Its even better if we use ksft_exit_fail_msg() which will print out "Bail
> out" meaning the test exited without completing. This string is TAP protocol
> specific.
This is debatable and not obviously correct. The documentation says:
Bail out!
As an emergency measure a test script can decide that further tests are
useless (e.g. missing dependencies) and testing should stop immediately. In
that case the test script prints the magic words
which suggests that a test should only emit "Bail out!" if it wants to stop
entirely. We definitely don't want KVM selftests to bail out if a TEST_ASSERT()
fails in one testcase.
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
> tools/testing/selftests/kvm/lib/assert.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/lib/assert.c b/tools/testing/selftests/kvm/lib/assert.c
> index 33651f5b3a7fd..db648a7ac429b 100644
> --- a/tools/testing/selftests/kvm/lib/assert.c
> +++ b/tools/testing/selftests/kvm/lib/assert.c
> @@ -87,7 +87,7 @@ test_assert(bool exp, const char *exp_str,
>
> if (errno == EACCES)
> ksft_exit_skip("Access denied - Exiting\n");
> - exit(254);
> + ksft_exit_fail_msg("\n");
> }
>
> return;
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-06-12 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 10:44 [PATCH 1/2] selftests: kvm: remove print_skip() Muhammad Usama Anjum
2024-06-12 10:44 ` [PATCH 2/2] selftests: kvm: replace exit() with ksft_exit_fail_msg() Muhammad Usama Anjum
2024-06-12 19:01 ` Sean Christopherson [this message]
2024-06-13 9:40 ` Muhammad Usama Anjum
2024-06-13 18:57 ` Sean Christopherson
2024-06-12 11:13 ` [PATCH 1/2] selftests: kvm: remove print_skip() Dev Jain
2024-06-12 18:10 ` Sean Christopherson
2024-06-15 13:01 ` kernel test robot
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=Zmnwhx0Y0qh0x03J@google.com \
--to=seanjc@google.com \
--cc=anup@brainfault.org \
--cc=imbrenda@linux.ibm.com \
--cc=kernel@collabora.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
/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