From: Oleg Nesterov <oleg@redhat.com>
To: fujo <hooyan2024@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] pidfs: don't report autoreaped tasks readable before exit info exists
Date: Sun, 18 Oct 2026 18:30:07 +0200 [thread overview]
Message-ID: <atT0D2l9iqMJHL3s@redhat.com> (raw)
In-Reply-To: <179226499044.847.6888435030853836469@gmail.com>
On 10/17, fujo wrote:
>
> Your POLLHUP remark resolves it: PIDFD_INFO_EXIT is published before the
> task linkage is removed, so POLLHUP is the right condition to wait for.
...
> I will withdraw the kernel patch and send a selftests-only v2.
Good ;)
> Do you
> think the CLONE_AUTOREAP cover letter or some KAPI comment should also
> say explicitly that POLLHUP, not POLLIN, guarantees that
> PIDFD_INFO_EXIT is available? The "poll the pidfd and retrieve the exit
> status via PIDFD_GET_INFO" wording is what led me there.
Well, I'm not quite sure which documentation you are referring to, but
of course it always makes sense to fix or improve the unclear doc.
Oleg.
prev parent reply other threads:[~2026-10-18 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 5:43 [RFC PATCH] pidfs: don't report autoreaped tasks readable before exit info exists fujo
2026-10-17 13:48 ` 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
2026-10-17 19:23 ` [RFC PATCH] pidfs: don't report autoreaped tasks readable before exit info exists fujo
2026-10-18 16:30 ` Oleg Nesterov [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=atT0D2l9iqMJHL3s@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=hooyan2024@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.