From: Mike Rapoport <rppt@kernel.org>
To: Hongfu Li <lihongfu@kylinos.cn>
Cc: akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, surenb@google.com,
mhocko@suse.com, shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] selftests/mm: use pkey_assert on clone_raw failure in pkey test
Date: Sun, 31 May 2026 17:36:25 +0300 [thread overview]
Message-ID: <ahxHaQFr3Uer2GBP@kernel.org> (raw)
In-Reply-To: <20260529071633.2807814-4-lihongfu@kylinos.cn>
Hi,
On Fri, May 29, 2026 at 03:16:32PM +0800, Hongfu Li wrote:
> Use pkey_assert(0) instead of perror("clone") when clone_raw() fails.
> The old path only printed an error and continued; the test now exits
> via pkey_assert() on failure so it does not hang or proceed with an
> invalid child.
Looks like clone() invocation changes in patch 2 belong here.
But is there actually a need to change ret = clone_raw() to
child_pid = clone_raw()?
> Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
> ---
> tools/testing/selftests/mm/pkey_sighandler_tests.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/pkey_sighandler_tests.c b/tools/testing/selftests/mm/pkey_sighandler_tests.c
> index 80b5b3dad86f..231dfb079075 100644
> --- a/tools/testing/selftests/mm/pkey_sighandler_tests.c
> +++ b/tools/testing/selftests/mm/pkey_sighandler_tests.c
> @@ -333,7 +333,7 @@ static void test_sigsegv_handler_with_different_pkey_for_stack(void)
>
> if (child_pid < 0) {
> errno = -child_pid;
> - perror("clone");
> + pkey_assert(0);
> } else if (child_pid == 0) {
> thread_segv_maperr_ptr(&sigstack);
> syscall_raw(SYS_exit, 0, 0, 0, 0, 0, 0);
> @@ -500,7 +500,7 @@ static void test_pkru_sigreturn(void)
>
> if (child_pid < 0) {
> errno = -child_pid;
> - perror("clone");
> + pkey_assert(0);
> } else if (child_pid == 0) {
> thread_sigusr2_self(&sigstack);
> syscall_raw(SYS_exit, 0, 0, 0, 0, 0, 0);
> --
> 2.50.1
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-05-31 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 7:16 [PATCH v4 0/4] selftests/mm: refactor pkey helpers and fix mmap error handling Hongfu Li
2026-05-29 7:16 ` [PATCH v4 1/4] selftests/mm: move pkey selftest helpers to pkey_util.c Hongfu Li
2026-05-29 8:12 ` Hongfu Li
2026-05-29 7:16 ` [PATCH v4 2/4] selftests/mm: unify pkey sighandler selftest assertions and tracing Hongfu Li
2026-05-31 14:31 ` Mike Rapoport
2026-05-29 7:16 ` [PATCH v4 3/4] selftests/mm: use pkey_assert on clone_raw failure in pkey test Hongfu Li
2026-05-31 14:36 ` Mike Rapoport [this message]
2026-06-01 5:32 ` Hongfu Li
2026-05-29 7:16 ` [PATCH v4 4/4] selftests/mm: add missing mmap() return checks in pkey tests Hongfu Li
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=ahxHaQFr3Uer2GBP@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=lihongfu@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.