From: Christian Brauner <brauner@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
Lennart Poettering <lennart@poettering.net>,
Daan De Meyer <daan.j.demeyer@gmail.com>,
Mike Yuan <me@yhndnzj.com>,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH RFC 2/2] selftests/pidfd: test multi-threaded exec polling
Date: Mon, 17 Mar 2025 16:00:44 +0100 [thread overview]
Message-ID: <20250317-work-pidfs-thread_group-v1-2-bc9e5ed283e9@kernel.org> (raw)
In-Reply-To: <20250317-work-pidfs-thread_group-v1-0-bc9e5ed283e9@kernel.org>
Ensure that during a multi-threaded exec and premature thread-group
leader exit no exit notification is generated.
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
tools/testing/selftests/pidfd/pidfd_info_test.c | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/tools/testing/selftests/pidfd/pidfd_info_test.c b/tools/testing/selftests/pidfd/pidfd_info_test.c
index 09bc4ae7aed5..e9a0aaf63e26 100644
--- a/tools/testing/selftests/pidfd/pidfd_info_test.c
+++ b/tools/testing/selftests/pidfd/pidfd_info_test.c
@@ -428,21 +428,22 @@ TEST_F(pidfd_info, thread_group_exec)
ASSERT_GE(pidfd_leader_thread, 0);
/*
- * We can poll and wait for the old thread-group leader to exit
- * using a thread-specific pidfd.
+ * We can't poll and wait for the old thread-group leader to exit
+ * using a thread-specific pidfd. The thread-group leader exited
+ * prematurely and notification is delayed until all subthreads
+ * have exited.
*
- * This only works until the thread has execed. When the thread
- * has execed it will have taken over the old thread-group
- * leaders struct pid. Calling poll after the thread execed will
- * thus block again because a new thread-group has started (Yes,
- * it's fscked.).
+ * When the thread has execed it will taken over the old
+ * thread-group leaders struct pid. Calling poll after the
+ * thread execed will thus block again because a new
+ * thread-group has started.
*/
fds.events = POLLIN;
fds.fd = pidfd_leader_thread;
- nevents = poll(&fds, 1, -1);
- ASSERT_EQ(nevents, 1);
- /* The thread-group leader has exited. */
- ASSERT_TRUE(!!(fds.revents & POLLIN));
+ nevents = poll(&fds, 1, 2000 /* wait 2 seconds */);
+ ASSERT_EQ(nevents, 0);
+ /* The thread-group leader has exited but there's still a live subthread. */
+ ASSERT_FALSE(!!(fds.revents & POLLIN));
/* The thread-group leader hasn't been reaped. */
ASSERT_FALSE(!!(fds.revents & POLLHUP));
--
2.47.2
prev parent reply other threads:[~2025-03-17 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 15:00 [PATCH RFC 0/2] pidfs: handle multi-threaded exec and premature thread-group leader exit Christian Brauner
2025-03-17 15:00 ` [PATCH RFC 1/2] pidfs: improve multi-threaded exec and premature thread-group leader exit polling Christian Brauner
2025-03-17 15:00 ` Christian Brauner [this message]
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=20250317-work-pidfs-thread_group-v1-2-bc9e5ed283e9@kernel.org \
--to=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=jlayton@kernel.org \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=oleg@redhat.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