From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Mark Brown <broonie@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Christian Brauner <brauner@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
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 1/2] tools/nolibc: Provide vfork()
Date: Mon, 9 Jun 2025 17:25:31 +0200 [thread overview]
Message-ID: <2ece41af-9500-447c-8203-5c57024e39f9@t-8ch.de> (raw)
In-Reply-To: <20250609-arm64-gcs-vfork-exit-v1-1-baad0f085747@kernel.org>
Hi Mark,
On 2025-06-09 16:08:56+0100, Mark Brown wrote:
> To allow testing of vfork() support in the arm64 basic-gcs test provide an
> implementation for nolibc, using the vfork() syscall if one is available
> and otherwise clone3(). We implement in terms of clone3() since the order
> of the arguments for clone() varies between architectures.
Thanks for the patch!
Do you want to take this series through your tree?
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> tools/include/nolibc/sys.h | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/tools/include/nolibc/sys.h b/tools/include/nolibc/sys.h
> index 9556c69a6ae1..e056da010f64 100644
> --- a/tools/include/nolibc/sys.h
> +++ b/tools/include/nolibc/sys.h
> @@ -22,6 +22,7 @@
> #include <linux/time.h>
> #include <linux/auxvec.h>
> #include <linux/fcntl.h> /* for O_* and AT_* */
> +#include <linux/sched.h> /* for clone_args */
> #include <linux/stat.h> /* for statx() */
>
> #include "errno.h"
> @@ -340,6 +341,34 @@ pid_t fork(void)
> return __sysret(sys_fork());
> }
>
> +#ifndef sys_vfork
> +static __attribute__((unused))
> +pid_t sys_vfork(void)
> +{
> +#ifdef __NR_vfork
> + return my_syscall0(__NR_vfork);
> +#elif defined(__NR_clone3)
> + /*
> + * clone() could be used but has different argument orders per
> + * architecture.
> + */
> + struct clone_args args = {
> + .flags = CLONE_VM | CLONE_VFORK,
> + .exit_signal = SIGCHLD,
> + };
> +
> + return my_syscall2(__NR_clone3, &args, sizeof(args));
> +#else
> + return __nolibc_enosys(__func__);
> +#endif
> +}
> +#endif
> +
> +static __attribute__((unused))
> +pid_t vfork(void)
> +{
> + return __sysret(sys_vfork());
> +}
Could you also add a test to nolibc-test.c?
Maybe extend test_fork() with a flag to use either fork() or vfork().
And maybe change the exit() in the test to _exit(); not that it would
make a difference for nolibc (yet).
>
> /*
> * int fsync(int fd);
>
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-06-09 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 15:08 [PATCH 0/2] kselftest/arm64: Add coverage for the interaction of vfork() and GCS Mark Brown
2025-06-09 15:08 ` [PATCH 1/2] tools/nolibc: Provide vfork() Mark Brown
2025-06-09 15:25 ` Thomas Weißschuh [this message]
2025-06-09 15:34 ` Thomas Weißschuh
2025-06-09 15:43 ` Mark Brown
2025-06-09 15:51 ` Thomas Weißschuh
2025-06-09 15:08 ` [PATCH 2/2] kselftest/arm64: Add a test for vfork() with GCS 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=2ece41af-9500-447c-8203-5c57024e39f9@t-8ch.de \
--to=linux@weissschuh.net \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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