From: "Carlos López" <clopez@suse.de>
To: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com, "Carlos López" <clopez@suse.de>,
"David Hildenbrand" <david@kernel.org>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Michal Hocko" <mhocko@suse.com>, "Shuah Khan" <shuah@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST
FRAMEWORK)
Subject: [PATCH] selftests/mm: pkeys: wait for the child in become_child()
Date: Fri, 6 Nov 2026 17:46:39 +0100 [thread overview]
Message-ID: <20261106164639.2959195-1-clopez@suse.de> (raw)
become_child() forks during test_pkey_alloc_exhaust() and has the parent
exit, so that the remaining tests run in the child. However, the test
runner only waits for the original process, so it sees the test finish
early with a success status while the remaining tests keep running in
the background. Failures after the first fork are thus not reported in
the exit status, and the remaining tests overlap with the next selftest.
Fix this by waiting for the child in the parent and exiting with its
status. A previous fix avoided waiting, arguing that the parents would
keep holding their resources [1]. Particularly, the parent keeps the
hugetlb reservation of its test memory, so the child runs out of hugetlb
pages after a few iterations. Avoid this by freeing the test memory
before waiting.
Link: https://lore.kernel.org/all/20240419115027.3848958-1-usama.anjum@collabora.com [1]
Fixes: e1812933b17b ("x86/selftests/pkeys: Fork() to check for state being preserved")
Signed-off-by: Carlos López <clopez@suse.de>
---
tools/testing/selftests/mm/protection_keys.c | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/mm/protection_keys.c b/tools/testing/selftests/mm/protection_keys.c
index b7882ab97683..5dece144ab95 100644
--- a/tools/testing/selftests/mm/protection_keys.c
+++ b/tools/testing/selftests/mm/protection_keys.c
@@ -1009,9 +1009,10 @@ static void test_pkey_syscalls_bad_args(int *ptr, u16 pkey)
pkey_assert(err);
}
-static void become_child(void)
+static void become_child(int *ptr)
{
pid_t forkret;
+ int status;
forkret = fork();
pkey_assert(forkret >= 0);
@@ -1021,7 +1022,16 @@ static void become_child(void)
/* in the child */
return;
}
- _exit(0);
+
+ /*
+ * Wait for the child to finish the tests and pass on its result.
+ * Free the test memory first, as it may reserve pages from the
+ * small hugetlb pool that the child needs.
+ */
+ free_pkey_malloc(ptr);
+ if (waitpid(forkret, &status, 0) != forkret || !WIFEXITED(status))
+ _exit(KSFT_FAIL);
+ _exit(WEXITSTATUS(status));
}
/* Assumes that all pkeys other than 'pkey' are unallocated */
@@ -1060,7 +1070,7 @@ static void test_pkey_alloc_exhaust(int *ptr, u16 pkey)
* preserved across fork().
*/
if (i == NR_PKEYS*2)
- become_child();
+ become_child(ptr);
}
dprintf3("%s()::%d\n", __func__, __LINE__);
base-commit: 843c58022865a7b0f9743416c2b48bc2632da23c
--
2.51.0
next reply other threads:[~2026-11-06 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:46 Carlos López [this message]
2026-11-06 21:57 ` Andrew Morton
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=20261106164639.2959195-1-clopez@suse.de \
--to=clopez@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--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=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--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 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®