From: Will Deacon <will@kernel.org>
To: Dorine Tipo <dorine.a.tipo@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH] selftests:arm64: Test PR_SVE_VL_INHERIT after a double fork
Date: Tue, 30 Apr 2024 13:20:32 +0100 [thread overview]
Message-ID: <20240430122032.GA13690@willie-the-truck> (raw)
In-Reply-To: <20240429044012.5018-1-dorine.a.tipo@gmail.com>
On Mon, Apr 29, 2024 at 04:40:12AM +0000, Dorine Tipo wrote:
> Add a new test, double_fork_test() to check the inheritance of the SVE
> vector length after a double fork.
> The `EXPECTED_TESTS` macro has been updated to account for this additional
> test.
> This patch addresses task 7 on the TODO list.
>
> Signed-off-by: Dorine Tipo <dorine.a.tipo@gmail.com>
> ---
> tools/testing/selftests/arm64/fp/za-fork.c | 95 +++++++++++++++++++++-
> 1 file changed, 94 insertions(+), 1 deletion(-)
I haven't tried compiling this, but some of the code looks a little off:
> diff --git a/tools/testing/selftests/arm64/fp/za-fork.c b/tools/testing/selftests/arm64/fp/za-fork.c
> index 587b94648222..35229e570dcf 100644
> --- a/tools/testing/selftests/arm64/fp/za-fork.c
> +++ b/tools/testing/selftests/arm64/fp/za-fork.c
> @@ -11,7 +11,7 @@
>
> #include "kselftest.h"
>
> -#define EXPECTED_TESTS 1
> +#define EXPECTED_TESTS 2
>
> int fork_test(void);
> int verify_fork(void);
> @@ -69,6 +69,97 @@ int fork_test_c(void)
> }
> }
>
> +int double_fork_test(void)
> +{
> + pid_t newpid, grandchild_pid, waiting;
> + int ret, child_status, parent_result;
> +
> + ret = prctl(PR_SVE_SET_VL, vl | PR_SVE_VL_INHERIT);
> + if (ret < 0)
> + ksft_exit_fail_msg("Failed to set SVE VL %d\n", vl);
> +
> + newpid = fork();
> + if (newpid == 0) {
> + /* In child */
> + if (!verify_fork()) {
> + ksft_print_msg("ZA state invalid in child\n");
> + exit(0);
> + }
> +
> + grandchild_pid = fork();
> + if (grandchild_pid == 0) {
> + /* in grandchild */
> + if (!verfy_fork()) {
> + ksft_print_msg("ZA state invalid in grandchild\n");
> + exit(0);
> + }
> +
> + ret = prctl(PR_SVE_GET_VL);
> + if (ret & PR_SVE_VL_INHERIT) {
> + ksft_print_msg("prctl() reports _INHERIT\n");
> + return;
Missing return value?
> + }
> + ksft_print_msg("prctl() does not report _INHERIT\n");
Indentation.
> +
> + } else if (grandchild_pid < 0) {
> + ksft_print_msg("fork() failed in first child: %d\n", grandchild_pid);
> + return 0;
> + }
> +
> + /* Wait for the grandchild process to exit */
> + waiting = waitpid(grandchild_pid, &child_status, 0);
> + if (waiting < 0) {
> + if (errno == EINTR)
> + continue;
'continue' outside of a loop?
> + ksft_print_msg("waitpid() failed: %d\n", errno);
> + return 0;
> + }
> + if (waiting != grandchild_pid) {
> + ksft_print_msg("waitpid() returned wrong PID\n");
> + return 0;
> + }
> +
> + if (!WIFEXITED(child_status)) {
> + ksft_print_msg("grandchild did not exit\n");
> + return 0;
> + }
> +
> + exit(1);
> + }
Stray '}' ?
Will
next prev parent reply other threads:[~2024-04-30 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 4:40 [PATCH] selftests:arm64: Test PR_SVE_VL_INHERIT after a double fork Dorine Tipo
2024-04-30 12:20 ` Will Deacon [this message]
2024-05-01 11:35 ` Dave Martin
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=20240430122032.GA13690@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dorine.a.tipo@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.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