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: [PATCH v2] selftests/pidfd: wait for POLLHUP before reading exit info
Date: Sun, 18 Oct 2026 21:27:43 +0200 [thread overview]
Message-ID: <atUdr2A9iJwl0Hbw@redhat.com> (raw)
In-Reply-To: <179234213014.649.13402722495876323247@gmail.com>
On 10/18, fujo wrote:
>
> You are right, thanks. That poll() is a liveness check, not an
> exit-info wait, so v3 keeps POLLIN there and only switches the polls
> that are followed by PIDFD_GET_INFO.
Great, I'll try to review V3 tomorrow.
> About the documentation: there is no in-tree KAPI file for this; the
> wording I referred to is the CLONE_AUTOREAP series description ("poll
> the child's exit via poll() and retrieve exit status via
> PIDFD_GET_INFO"). If you or Christian think a clarifying sentence
> belongs somewhere in the tree, I'm happy to send it, but I didn't want
> to guess where.
So it seems that (please correct me if I am wrong) you were confused by
some wording in a changelog or cover letter. If yes, too late to fix it.
But perhaps you can check (and possibly fix/improve) the man page(s) ?
Though, to be honest, I have no idea where all of this is documented...
But surely it must be documented somewhere, right ? ;)
Thanks,
Oleg.
prev parent reply other threads:[~2026-10-18 19:27 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 ` 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 [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=atUdr2A9iJwl0Hbw@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 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®