From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <edumazet@google.com>,
<pabeni@redhat.com>, Mark Brown <broonie@kernel.org>,
<ivan.orlov0322@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
<shuah@kernel.org>, <jglisse@redhat.com>,
<akpm@linux-foundation.org>, <keescook@chromium.org>,
<linux-sound@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [PATCH net-next] selftests: avoid using SKIP(exit()) in harness fixure setup
Date: Tue, 5 Mar 2024 16:54:37 +0100 [thread overview]
Message-ID: <24a1f5df-1629-4569-ac1e-b7c9a128f0c7@intel.com> (raw)
In-Reply-To: <20240304233621.646054-1-kuba@kernel.org>
On 3/5/24 00:36, Jakub Kicinski wrote:
> selftest harness uses various exit codes to signal test
> results. Avoid calling exit() directly, otherwise tests
> may get broken by harness refactoring (like the commit
> under Fixes). SKIP() will instruct the harness that the
> test shouldn't run, it used to not be the case, but that
> has been fixed. So just return, no need to exit.
>
> Note that for hmm-tests this actually changes the result
> from pass to skip. Which seems fair, the test is skipped,
> after all.
>
> Reported-by: Mark Brown <broonie@kernel.org>
> Link: https://lore.kernel.org/all/05f7bf89-04a5-4b65-bf59-c19456aeb1f0@sirena.org.uk
> Fixes: a724707976b0 ("selftests: kselftest_harness: use KSFT_* exit codes")
I believe that the next patch of the linked series is a culprit,
but that does not mandate a next revision in my eyes
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> This needs to go to net-next because that's where the breaking
> patch was (mis?)-applied.
>
> CC: ivan.orlov0322@gmail.com
> CC: perex@perex.cz
> CC: tiwai@suse.com
> CC: broonie@kernel.org
> CC: shuah@kernel.org
> CC: jglisse@redhat.com
> CC: akpm@linux-foundation.org
> CC: keescook@chromium.org
> CC: linux-sound@vger.kernel.org
> CC: linux-kselftest@vger.kernel.org
> CC: linux-mm@kvack.org
> ---
> tools/testing/selftests/alsa/test-pcmtest-driver.c | 4 ++--
> tools/testing/selftests/mm/hmm-tests.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/alsa/test-pcmtest-driver.c b/tools/testing/selftests/alsa/test-pcmtest-driver.c
> index a52ecd43dbe3..ca81afa4ee90 100644
> --- a/tools/testing/selftests/alsa/test-pcmtest-driver.c
> +++ b/tools/testing/selftests/alsa/test-pcmtest-driver.c
> @@ -127,11 +127,11 @@ FIXTURE_SETUP(pcmtest) {
> int err;
>
> if (geteuid())
> - SKIP(exit(-1), "This test needs root to run!");
> + SKIP(return, "This test needs root to run!");
>
> err = read_patterns();
> if (err)
> - SKIP(exit(-1), "Can't read patterns. Probably, module isn't loaded");
> + SKIP(return, "Can't read patterns. Probably, module isn't loaded");
>
> card_name = malloc(127);
> ASSERT_NE(card_name, NULL);
> diff --git a/tools/testing/selftests/mm/hmm-tests.c b/tools/testing/selftests/mm/hmm-tests.c
> index 20294553a5dd..d2cfc9b494a0 100644
> --- a/tools/testing/selftests/mm/hmm-tests.c
> +++ b/tools/testing/selftests/mm/hmm-tests.c
> @@ -138,7 +138,7 @@ FIXTURE_SETUP(hmm)
>
> self->fd = hmm_open(variant->device_number);
> if (self->fd < 0 && hmm_is_coherent_type(variant->device_number))
> - SKIP(exit(0), "DEVICE_COHERENT not available");
> + SKIP(return, "DEVICE_COHERENT not available");
> ASSERT_GE(self->fd, 0);
> }
>
> @@ -149,7 +149,7 @@ FIXTURE_SETUP(hmm2)
>
> self->fd0 = hmm_open(variant->device_number0);
> if (self->fd0 < 0 && hmm_is_coherent_type(variant->device_number0))
> - SKIP(exit(0), "DEVICE_COHERENT not available");
> + SKIP(return, "DEVICE_COHERENT not available");
> ASSERT_GE(self->fd0, 0);
> self->fd1 = hmm_open(variant->device_number1);
> ASSERT_GE(self->fd1, 0);
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
- that's totally what mandates vfork() introduced in recent refactor
(Sorry for pointing the same in the Link:-ed thread, it was just
newer/higher in my email client)
next prev parent reply other threads:[~2024-03-05 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 23:36 Jakub Kicinski
2024-03-05 0:49 ` Kees Cook
2024-03-05 15:32 ` Mark Brown
2024-03-05 15:54 ` Przemek Kitszel [this message]
2024-03-06 3:40 ` patchwork-bot+netdevbpf
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=24a1f5df-1629-4569-ac1e-b7c9a128f0c7@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivan.orlov0322@gmail.com \
--cc=jglisse@redhat.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sound@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=perex@perex.cz \
--cc=shuah@kernel.org \
--cc=tiwai@suse.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