From: Kees Cook <keescook@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
Eric Biederman <ebiederm@xmission.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 2/2] selftests/exec: Convert execveat test to generate KTAP output
Date: Thu, 28 Sep 2023 17:48:34 -0700 [thread overview]
Message-ID: <202309281748.7BAE187A@keescook> (raw)
In-Reply-To: <20230928-ktap-exec-v1-2-1013a2db0426@kernel.org>
On Thu, Sep 28, 2023 at 04:38:12PM +0200, Mark Brown wrote:
> Currently the execveat test does not produce KTAP output but rather a
> custom format. This means that we only get a pass/fail for the suite, not
> for each individual test that the suite does. Convert to using the standard
> kselftest output functions which result in KTAP output being generated.
>
> The main trick with this is that, being an exec() related test, the
> program executes itself and returns specific exit codes to verify
> success meaning that we need to only use the top level kselftest
> header/summary functions when invoked directly rather than when run as
> part of a test.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Yay! More KTAP! :)
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
prev parent reply other threads:[~2023-09-29 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 14:38 [PATCH 0/2] kselftest/exec: Convert execveat test to " Mark Brown
2023-09-28 14:38 ` [PATCH 1/2] kselftest: Add a ksft_perror() helper Mark Brown
2023-09-29 0:48 ` Kees Cook
2023-09-29 7:50 ` Mark Brown
2023-09-29 17:31 ` Kees Cook
2023-10-01 10:24 ` Mark Brown
2023-09-28 14:38 ` [PATCH 2/2] selftests/exec: Convert execveat test to generate KTAP output Mark Brown
2023-09-29 0:48 ` Kees Cook [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=202309281748.7BAE187A@keescook \
--to=keescook@chromium.org \
--cc=broonie@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
/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