From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <brauner@kernel.org>
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>
Subject: Re: [PATCH v3 00/16] pidfs: provide information after task has been reaped
Date: Wed, 5 Mar 2025 13:06:35 +0100 [thread overview]
Message-ID: <20250305120622.GA30741@redhat.com> (raw)
In-Reply-To: <20250305-work-pidfs-kill_on_last_close-v3-0-c8c3d8361705@kernel.org>
On 03/05, Christian Brauner wrote:
>
> Christian Brauner (16):
> pidfs: switch to copy_struct_to_user()
> pidfd: rely on automatic cleanup in __pidfd_prepare()
> pidfs: move setting flags into pidfs_alloc_file()
> pidfs: use private inode slab cache
> pidfs: record exit code and cgroupid at exit
> pidfs: allow to retrieve exit information
> selftests/pidfd: fix header inclusion
> pidfs/selftests: ensure correct headers for ioctl handling
> selftests/pidfd: expand common pidfd header
> selftests/pidfd: add first PIDFD_INFO_EXIT selftest
> selftests/pidfd: add second PIDFD_INFO_EXIT selftest
> selftests/pidfd: add third PIDFD_INFO_EXIT selftest
> selftests/pidfd: add fourth PIDFD_INFO_EXIT selftest
> selftests/pidfd: add fifth PIDFD_INFO_EXIT selftest
> selftests/pidfd: add sixth PIDFD_INFO_EXIT selftest
> selftests/pidfd: add seventh PIDFD_INFO_EXIT selftest
I see nothing wrong in V3. For 1-6
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2025-03-05 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:08 [PATCH v3 00/16] pidfs: provide information after task has been reaped Christian Brauner
2025-03-05 10:08 ` [PATCH v3 01/16] pidfs: switch to copy_struct_to_user() Christian Brauner
2025-03-05 10:08 ` [PATCH v3 02/16] pidfd: rely on automatic cleanup in __pidfd_prepare() Christian Brauner
2025-03-05 10:08 ` [PATCH v3 03/16] pidfs: move setting flags into pidfs_alloc_file() Christian Brauner
2025-03-05 10:08 ` [PATCH v3 04/16] pidfs: use private inode slab cache Christian Brauner
2025-03-05 10:08 ` [PATCH v3 05/16] pidfs: record exit code and cgroupid at exit Christian Brauner
2025-03-05 10:08 ` [PATCH v3 06/16] pidfs: allow to retrieve exit information Christian Brauner
2025-03-09 13:25 ` Mike Yuan
2025-03-05 10:08 ` [PATCH v3 07/16] selftests/pidfd: fix header inclusion Christian Brauner
2025-03-05 10:08 ` [PATCH v3 08/16] pidfs/selftests: ensure correct headers for ioctl handling Christian Brauner
2025-03-05 10:08 ` [PATCH v3 09/16] selftests/pidfd: expand common pidfd header Christian Brauner
2025-03-05 10:08 ` [PATCH v3 10/16] selftests/pidfd: add first PIDFD_INFO_EXIT selftest Christian Brauner
2025-03-05 10:08 ` [PATCH v3 11/16] selftests/pidfd: add second " Christian Brauner
2025-03-05 10:08 ` [PATCH v3 12/16] selftests/pidfd: add third " Christian Brauner
2025-03-05 10:08 ` [PATCH v3 13/16] selftests/pidfd: add fourth " Christian Brauner
2025-03-05 10:08 ` [PATCH v3 14/16] selftests/pidfd: add fifth " Christian Brauner
2025-03-05 10:08 ` [PATCH v3 15/16] selftests/pidfd: add sixth " Christian Brauner
2025-03-05 10:08 ` [PATCH v3 16/16] selftests/pidfd: add seventh " Christian Brauner
2025-03-05 12:06 ` Oleg Nesterov [this message]
2025-03-05 12:20 ` [PATCH v3 00/16] pidfs: provide information after task has been reaped Christian Brauner
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=20250305120622.GA30741@redhat.com \
--to=oleg@redhat.com \
--cc=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 \
/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.