From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: align sys_vfork() with sys_fork()
Date: Mon, 5 Jan 2026 08:46:49 +0100 [thread overview]
Message-ID: <aVtsaXvnbmAILPu1@1wt.eu> (raw)
In-Reply-To: <20260104-nolibc-vfork-v1-1-a63464b9e4e6@weissschuh.net>
On Sun, Jan 04, 2026 at 11:43:13PM +0100, Thomas Weißschuh wrote:
> Currently the generic variants of sys_fork() and sys_vfork() differ in
> both they precedence of used system calls and the usage of sys_clone()
> vs sys_clone3(). While the interface of clone3() in sys_vfork() is more
> consistent over different architectures, qemu-user does not support it,
> making testing harder. We already handle the different clone()
> interfaces for sys_fork() in the architecture-specific headers, and can
> do so also for sys_vfork(). In fact SPARC already has such handling and
> only s390 is currently missing.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
LGTM.
Acked-by: Willy Tarreau <w@1wt.eu>
thanks,
Willy
prev parent reply other threads:[~2026-01-05 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 22:43 [PATCH] tools/nolibc: align sys_vfork() with sys_fork() Thomas Weißschuh
2026-01-05 7:46 ` Willy Tarreau [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=aVtsaXvnbmAILPu1@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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