From: Kevin Brodsky <kevin.brodsky@arm.com>
To: Hongfu Li <lihongfu@kylinos.cn>,
akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, shuah@kernel.org
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, keith.lucas@oracle.com,
maddy@linux.ibm.com, usama.anjum@collabora.com,
yury.khrustalev@arm.com, jhubbard@nvidia.com, joey.gouly@arm.com,
zwisler@google.com, hongfu.li@linux.dev
Subject: Re: [PATCH v8 3/5] selftests/mm: use pkey_assert on clone_raw failure in pkey test
Date: Wed, 1 Jul 2026 10:48:31 +0200 [thread overview]
Message-ID: <8ad9d4ed-939b-4e93-bfb8-fcf1a19c00db@arm.com> (raw)
In-Reply-To: <20260630073235.3802271-4-lihongfu@kylinos.cn>
On 30/06/2026 09:32, 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.
>
> Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
Reviewed-by: Kevin Brodsky <kevin.brodsky@arm.com>
> ---
> 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 085e771227fb..882928f2912b 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 (ret < 0) {
> errno = -ret;
> - perror("clone");
> + pkey_assert(0);
> } else if (ret == 0) {
> thread_segv_maperr_ptr(&sigstack);
> syscall_raw(SYS_exit, 0, 0, 0, 0, 0, 0);
> @@ -506,7 +506,7 @@ static void test_pkru_sigreturn(void)
>
> if (ret < 0) {
> errno = -ret;
> - perror("clone");
> + pkey_assert(0);
> } else if (ret == 0) {
> thread_sigusr2_self(&sigstack);
> syscall_raw(SYS_exit, 0, 0, 0, 0, 0, 0);
next prev parent reply other threads:[~2026-07-01 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:32 [PATCH v8 0/5] selftests/mm: refactor pkey helpers and fix mmap error handling Hongfu Li
2026-06-30 7:32 ` [PATCH v8 1/5] selftests/mm: move pkey selftest helpers to pkey_util.c Hongfu Li
2026-07-01 8:46 ` Kevin Brodsky
2026-06-30 7:32 ` [PATCH v8 2/5] selftests/mm: unify pkey sighandler selftest assertions and tracing Hongfu Li
2026-07-01 8:48 ` Kevin Brodsky
2026-07-01 10:33 ` Hongfu Li
2026-06-30 7:32 ` [PATCH v8 3/5] selftests/mm: use pkey_assert on clone_raw failure in pkey test Hongfu Li
2026-07-01 8:48 ` Kevin Brodsky [this message]
2026-06-30 7:32 ` [PATCH v8 4/5] selftests/mm: add missing mmap() return checks in pkey tests Hongfu Li
2026-07-01 8:48 ` Kevin Brodsky
2026-06-30 7:32 ` [PATCH v8 5/5] selftests/mm: add missing pthread_create() " Hongfu Li
2026-07-01 8:49 ` Kevin Brodsky
2026-06-30 17:56 ` [PATCH v8 0/5] selftests/mm: refactor pkey helpers and fix mmap error handling Mike Rapoport
2026-06-30 19:05 ` Liam R. Howlett
2026-07-01 5:20 ` Andrew Morton
2026-07-01 6:59 ` Kevin Brodsky
2026-07-01 9:33 ` Hongfu Li
2026-07-01 15:12 ` Kevin Brodsky
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=8ad9d4ed-939b-4e93-bfb8-fcf1a19c00db@arm.com \
--to=kevin.brodsky@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hongfu.li@linux.dev \
--cc=jhubbard@nvidia.com \
--cc=joey.gouly@arm.com \
--cc=keith.lucas@oracle.com \
--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=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.anjum@collabora.com \
--cc=vbabka@kernel.org \
--cc=yury.khrustalev@arm.com \
--cc=zwisler@google.com \
/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
all inboxes | Powered by JetHome®