From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Shuah Khan" <shuah@kernel.org>, "Kees Cook" <kees@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Yuwen Chen <ywen.chen@foxmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 0/5] selftests: harness: Detect illegal mixing of kselftest and harness functionality
Date: Tue, 31 Mar 2026 13:50:07 -0600 [thread overview]
Message-ID: <0d513cae-e928-454c-9629-a798fb08e2cd@linuxfoundation.org> (raw)
In-Reply-To: <20260302-kselftest-harness-v2-0-3143aa41d989@linutronix.de>
On 3/2/26 07:13, Thomas Weißschuh wrote:
> Users may accidentally use the kselftest_test_result_*() functions in
> their harness tests. If ksft_finished() is not used, the results
> reported in this way are silently ignored.
>
> Detect such cases and fail the test.
>
> This should probably only go in during the next cycle.
>
Applied to linux-kselftest next for Linux 7.1-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2026-03-31 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:13 [PATCH v2 0/5] selftests: harness: Detect illegal mixing of kselftest and harness functionality Thomas Weißschuh
2026-03-02 14:13 ` [PATCH v2 1/5] selftests: kselftest: Treat xpass as successful result Thomas Weißschuh
2026-03-02 14:13 ` [PATCH v2 2/5] selftests: harness: Validate that explicit kselftest exitcodes are handled Thomas Weißschuh
2026-03-02 14:13 ` [PATCH v2 3/5] selftests: kselftest: Add ksft_reset_state() Thomas Weißschuh
2026-03-02 14:13 ` [PATCH v2 4/5] selftests: harness: Detect illegal mixing of kselftest and harness functionality Thomas Weißschuh
2026-03-02 14:13 ` [PATCH v2 5/5] selftests: harness: Validate intermixing " Thomas Weißschuh
2026-03-31 19:50 ` Shuah Khan [this message]
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=0d513cae-e928-454c-9629-a798fb08e2cd@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=wad@chromium.org \
--cc=ywen.chen@foxmail.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