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 v3 0/4] kselftest/arm64: Add coverage for the interaction of vfork() and GCS
Date: Fri, 4 Jul 2025 13:27:28 +0200 [thread overview]
Message-ID: <f438fc60-e602-4301-a7dd-bee43c020720@t-8ch.de> (raw)
In-Reply-To: <20250703-arm64-gcs-vfork-exit-v3-0-1e9a9d2ddbbe@kernel.org>
On 2025-07-03 17:00:14+0100, Mark Brown wrote:
> I had cause to look at the vfork() support for GCS and realised that we
> don't have any direct test coverage, this series does so by adding
> vfork() to nolibc and then using that in basic-gcs to provide some
> simple vfork() coverage.
Thanks. I applied the patches, but moved the arm64 selftest patch to be
the last one.
FYI nolibc now has a proper prctl() implementation you might want to use.
Also your vfork() selftest uncovered a bug in the brandnew SuperH support.
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Changes in v3:
> - Stylistic nits in the GCS vfork() test.
> - SPARC has a non-standard vfork() ABI which needs handling.
> - Link to v2: https://lore.kernel.org/r/20250610-arm64-gcs-vfork-exit-v2-0-929443dfcf82@kernel.org
>
> Changes in v2:
> - Add replacement of ifdef with if defined() in nolibc since the code
> doesn't reflect the coding style.
> - Remove check for arch specific vfork().
> - Link to v1: https://lore.kernel.org/r/20250609-arm64-gcs-vfork-exit-v1-0-baad0f085747@kernel.org
>
> ---
> Mark Brown (4):
> tools/nolibc: Replace ifdef with if defined() in sys.h
> tools/nolibc: Provide vfork()
> kselftest/arm64: Add a test for vfork() with GCS
> selftests/nolibc: Add coverage of vfork()
>
> tools/include/nolibc/arch-sparc.h | 16 +++++++
> tools/include/nolibc/sys.h | 59 ++++++++++++++++++-------
> tools/testing/selftests/arm64/gcs/basic-gcs.c | 63 +++++++++++++++++++++++++++
> tools/testing/selftests/nolibc/nolibc-test.c | 23 ++++++++--
> 4 files changed, 142 insertions(+), 19 deletions(-)
> ---
> base-commit: 86731a2a651e58953fc949573895f2fa6d456841
> change-id: 20250528-arm64-gcs-vfork-exit-4a7daf7652ee
>
> Best regards,
> --
> Mark Brown <broonie@kernel.org>
>
next prev parent reply other threads:[~2025-07-04 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 16:00 [PATCH v3 0/4] kselftest/arm64: Add coverage for the interaction of vfork() and GCS Mark Brown
2025-07-03 16:00 ` [PATCH v3 1/4] tools/nolibc: Replace ifdef with if defined() in sys.h Mark Brown
2025-07-03 16:00 ` [PATCH v3 2/4] tools/nolibc: Provide vfork() Mark Brown
2025-07-03 16:00 ` [PATCH v3 3/4] kselftest/arm64: Add a test for vfork() with GCS Mark Brown
2025-07-03 16:00 ` [PATCH v3 4/4] selftests/nolibc: Add coverage of vfork() Mark Brown
2025-07-04 11:27 ` Thomas Weißschuh [this message]
2025-07-04 12:02 ` [PATCH v3 0/4] kselftest/arm64: Add coverage for the interaction of vfork() and 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=f438fc60-e602-4301-a7dd-bee43c020720@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