From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Christian Brauner" <brauner@kernel.org>,
"Will Deacon" <will@kernel.org>, "Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 3/4] kselftest/arm64: Add a test for vfork() with GCS
Date: Thu, 3 Jul 2025 11:39:14 +0100 [thread overview]
Message-ID: <aGZd0vdu8PpLKfX1@arm.com> (raw)
In-Reply-To: <20250610-arm64-gcs-vfork-exit-v2-3-929443dfcf82@kernel.org>
On Tue, Jun 10, 2025 at 01:29:46PM +0100, Mark Brown wrote:
> diff --git a/tools/testing/selftests/arm64/gcs/basic-gcs.c b/tools/testing/selftests/arm64/gcs/basic-gcs.c
> index 3fb9742342a3..96ea51cf7163 100644
> --- a/tools/testing/selftests/arm64/gcs/basic-gcs.c
> +++ b/tools/testing/selftests/arm64/gcs/basic-gcs.c
> @@ -298,6 +298,68 @@ static bool test_fork(void)
> return pass;
> }
>
> +/* A vfork()ed process can run and exit */
> +static bool test_vfork(void)
> +{
> + unsigned long child_mode;
> + int ret, status;
> + pid_t pid;
> + bool pass = true;
> +
> + pid = vfork();
> + if (pid == -1) {
> + ksft_print_msg("vfork() failed: %d\n", errno);
> + pass = false;
> + goto out;
> + }
> + if (pid == 0) {
> + /* In child, make sure we can call a function, read
> + * the GCS pointer and status and then exit */
Nit: coding style for multi-line comment. I guess we follow the kernel
style.
> + valid_gcs_function();
> + get_gcspr();
> +
> + ret = my_syscall5(__NR_prctl, PR_GET_SHADOW_STACK_STATUS,
> + &child_mode, 0, 0, 0);
> + if (ret == 0 && !(child_mode & PR_SHADOW_STACK_ENABLE)) {
> + ksft_print_msg("GCS not enabled in child\n");
> + ret = -EINVAL;
Does it make sense in user-space to pass negative values to exit()? I
thought it should be between 0 and 255.
> + }
> +
> + exit(ret);
Should this be _exit() instead? IIRC exit() does some clean-ups which
are not safe in the vfork'ed child.
> + }
> +
> + /*
> + * In parent, check we can still do function calls then block
> + * for the child.
> + */
The comment "block for the child" doesn't make sense in this context.
vfork() already blocks the parent until exec() or _exit(). But I can see
why you wanted waitpid() to retrieve the return status.
> + valid_gcs_function();
> +
> + ksft_print_msg("Waiting for child %d\n", pid);
> +
> + ret = waitpid(pid, &status, 0);
> + if (ret == -1) {
> + ksft_print_msg("Failed to wait for child: %d\n",
> + errno);
> + return false;
> + }
> +
> + if (!WIFEXITED(status)) {
> + ksft_print_msg("Child exited due to signal %d\n",
> + WTERMSIG(status));
> + pass = false;
> + } else {
> + if (WEXITSTATUS(status)) {
Nit: } else if {
> + ksft_print_msg("Child exited with status %d\n",
> + WEXITSTATUS(status));
> + pass = false;
> + }
> + }
> +
> +out:
> +
> + return pass;
> +}
> +
> typedef bool (*gcs_test)(void);
>
> static struct {
> @@ -314,6 +376,7 @@ static struct {
> { "enable_invalid", enable_invalid, true },
> { "map_guarded_stack", map_guarded_stack },
> { "fork", test_fork },
> + { "vfork", test_vfork },
> };
>
> int main(void)
Other than the above, feel free add
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Thomas, do you want to merge this via your tree? Thanks.
--
Catalin
next prev parent reply other threads:[~2025-07-03 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:29 [PATCH v2 0/4] kselftest/arm64: Add coverage for the interaction of vfork() and GCS Mark Brown
2025-06-10 12:29 ` [PATCH v2 1/4] tools/nolibc: Replace ifdef with if defined() in sys.h Mark Brown
2025-06-10 12:29 ` [PATCH v2 2/4] tools/nolibc: Provide vfork() Mark Brown
2025-06-10 16:42 ` Thomas Weißschuh
2025-06-10 12:29 ` [PATCH v2 3/4] kselftest/arm64: Add a test for vfork() with GCS Mark Brown
2025-07-03 10:39 ` Catalin Marinas [this message]
2025-07-03 11:19 ` Mark Brown
2025-06-10 12:29 ` [PATCH v2 4/4] selftests/nolibc: Add coverage of vfork() Mark Brown
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=aGZd0vdu8PpLKfX1@arm.com \
--to=catalin.marinas@arm.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).