From: fujo <hooyan2024@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: brauner@kernel.org, oleg@redhat.com, viro@zeniv.linux.org.uk,
jack@suse.cz, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] pidfs: don't report autoreaped tasks readable before exit info exists
Date: Sat, 17 Oct 2026 01:43:56 -0400 [thread overview]
Message-ID: <20261017054356.7874-1-hooyan2024@gmail.com> (raw)
pidfd_poll() reports a task readable as soon as task->exit_state is set
and the thread group is empty. For a task that is going to be
auto-reaped (CLONE_AUTOREAP, or a parent that ignores SIGCHLD) this
happens before release_task() runs and before pidfs_exit() publishes
PIDFS_ATTR_BIT_EXIT.
A woken poller that immediately calls PIDFD_GET_INFO with
PIDFD_INFO_EXIT can therefore get an answer without PIDFD_INFO_EXIT.
For CLONE_AUTOREAP this breaks the documented use of polling the pidfd
and retrieving the exit status via PIDFD_GET_INFO: the task is
auto-reaped and cannot be waited for, so the exit status is lost for
that poll.
Do not report a task that is pending auto-reap readable until its exit
information has been published, and wake the pidfd waitqueue from
pidfs_exit() after PIDFS_ATTR_BIT_EXIT has been set so that pollers
woken early sleep again and are woken once the information exists.
Reproducer: clone3(CLONE_PIDFD | CLONE_AUTOREAP); the child creates a
thread that exits after 500us and then exits itself; the parent polls
the pidfd and immediately calls PIDFD_GET_INFO with PIDFD_INFO_EXIT.
On current mainline 18/300 iterations (SMP 2) and 78/300 (SMP 1) return
POLLIN without PIDFD_INFO_EXIT; with this change 0/300 in both cases.
The in-tree pidfd_autoreap_test global.autoreap_multithreaded case
fails without and passes with this change.
Signed-off-by: fujo <hooyan2024@gmail.com>
---
fs/pidfs.c | 29 +++++++++++++++++++++++++++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git a/fs/pidfs.c b/fs/pidfs.c
index a6a643f15..5245131ea 100644
--- a/fs/pidfs.c
+++ b/fs/pidfs.c
@@ -320,8 +320,26 @@ static __poll_t pidfd_poll(struct file *file, struct poll_table_struct *pts)
task = pid_task(pid, PIDTYPE_PID);
if (!task)
poll_flags = EPOLLIN | EPOLLRDNORM | EPOLLHUP;
- else if (task->exit_state && !delay_group_leader(task))
- poll_flags = EPOLLIN | EPOLLRDNORM;
+ else if (task->exit_state && !delay_group_leader(task)) {
+ struct pidfs_attr *pattr = READ_ONCE(pid->attr);
+ bool pending_autoreap;
+
+ /*
+ * A task that is going to be auto-reaped reaches EXIT_DEAD (or
+ * carries CLONE_AUTOREAP) before release_task() publishes
+ * PIDFS_ATTR_BIT_EXIT. Don't report readable until the exit
+ * information is actually available, or a poller can observe
+ * POLLIN and then get PIDFD_GET_INFO without PIDFD_INFO_EXIT.
+ * ptraced tasks are not auto-reaped, so they keep the old
+ * behavior.
+ */
+ pending_autoreap = (!task->ptrace && task->signal->autoreap) ||
+ task->exit_state == EXIT_DEAD;
+ if (!pending_autoreap ||
+ (!IS_ERR_OR_NULL(pattr) &&
+ test_bit(PIDFS_ATTR_BIT_EXIT, &pattr->attr_mask)))
+ poll_flags = EPOLLIN | EPOLLRDNORM;
+ }
return poll_flags;
}
@@ -790,6 +808,13 @@ void pidfs_exit(struct task_struct *tsk)
/* Ensure that PIDFD_GET_INFO sees either all or nothing. */
smp_wmb();
set_bit(PIDFS_ATTR_BIT_EXIT, &attr->attr_mask);
+
+ /*
+ * Pollers may have been woken before the exit information above was
+ * published. Wake them again now that PIDFD_GET_INFO can return
+ * PIDFD_INFO_EXIT.
+ */
+ do_notify_pidfd(tsk);
}
#ifdef CONFIG_COREDUMP
--
2.53.0
next reply other threads:[~2026-10-17 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 5:43 fujo [this message]
2026-10-17 13:48 ` Oleg Nesterov
2026-10-17 19:23 ` fujo
2026-10-18 16:30 ` Oleg Nesterov
2026-10-17 19:23 ` [PATCH v2] selftests/pidfd: wait for POLLHUP before reading exit info fujo
2026-10-18 16:25 ` Oleg Nesterov
2026-10-18 16:48 ` [PATCH v3] " fujo
2026-10-18 16:48 ` [PATCH v2] " fujo
2026-10-18 19:27 ` Oleg Nesterov
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=20261017054356.7874-1-hooyan2024@gmail.com \
--to=hooyan2024@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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®