From: Christian Brauner <brauner@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Halaney <andrew@amutable.com>
Cc: Christian Brauner <brauner@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Eric Dumazet <edumazet@kernel.org>
Subject: Re: [PATCH v4 00/10] net: support thread-specific pidfds for send and connect
Date: Mon, 12 Oct 2026 11:00:25 +0200 [thread overview]
Message-ID: <20261012-panik-helligkeitsgrad-hackfleisch-c9830fcaf7fc@brauner> (raw)
In-Reply-To: <20261005-work-unix-passpidfd-v4-0-350183b6e02a@amutable.com>
On Mon, 05 Oct 2026 10:09:30 -0500, Andrew Halaney wrote:
> SO_PASSPIDFD/SCM_PIDFD and SO_PEERPIDFD allow to retrieve a pidfd for
> the thread-group leader. The coredump server using the coredump socket
> cannot get a handle on the task that took the signal and is writing the
> coredump easily. Workloads interested in per-thread authentification
> have similar problems.
>
> Add SO_PASSPIDFD_THREAD/SCM_PIDFD_THREAD and SO_PEERPIDFD_THREAD. We
> record the sending and the connecting thread in addition to the
> thread-group leader.
>
> [...]
Ok, stable branch it is as discussed.
---
Applied to the vfs-7.4.shared.net-next.pidfd branch of the vfs/vfs.git tree.
Patches in the vfs-7.4.shared.net-next.pidfd branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.4.shared.net-next.pidfd
[01/10] pid: add helpers to operate on a struct pid array
https://git.kernel.org/vfs/vfs/c/fd0349aadbb9
[02/10] af_unix: record the pid of the sending thread
https://git.kernel.org/vfs/vfs/c/c48ae5bcfc35
[03/10] net: add SO_PASSPIDFD_THREAD to get a thread-specific SCM_PIDFD
https://git.kernel.org/vfs/vfs/c/be3a5e06b962
[04/10] selftests/net: SO_PASSPIDFD_THREAD
https://git.kernel.org/vfs/vfs/c/4e2446c83f38
[05/10] net: turn sk_peer_pid into an array indexed by pid type
https://git.kernel.org/vfs/vfs/c/95d9b7369665
[06/10] af_unix: record the pid of the connecting thread
https://git.kernel.org/vfs/vfs/c/1592d89361e9
[07/10] net: add SO_PEERPIDFD_THREAD to get a thread-specific pidfd
https://git.kernel.org/vfs/vfs/c/e10899b2a098
[08/10] selftests/net: SO_PEERPIDFD_THREAD
https://git.kernel.org/vfs/vfs/c/02e658dffe50
[09/10] pidfs: record the coredump on the dumping thread's pid too
https://git.kernel.org/vfs/vfs/c/3209535cd39e
[10/10] selftests/coredump: check the dumping thread's pidfd
https://git.kernel.org/vfs/vfs/c/1f47b275d5d5
next prev parent reply other threads:[~2026-10-12 9:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:09 Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 01/10] pid: add helpers to operate on a struct pid array Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 02/10] af_unix: record the pid of the sending thread Andrew Halaney
2026-10-08 4:35 ` Kuniyuki Iwashima
2026-10-05 15:09 ` [PATCH v4 03/10] net: add SO_PASSPIDFD_THREAD to get a thread-specific SCM_PIDFD Andrew Halaney
2026-10-08 4:36 ` Kuniyuki Iwashima
2026-10-05 15:09 ` [PATCH v4 04/10] selftests/net: SO_PASSPIDFD_THREAD Andrew Halaney
2026-10-08 5:03 ` Kuniyuki Iwashima
2026-10-05 15:09 ` [PATCH v4 05/10] net: turn sk_peer_pid into an array indexed by pid type Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 06/10] af_unix: record the pid of the connecting thread Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 07/10] net: add SO_PEERPIDFD_THREAD to get a thread-specific pidfd Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 08/10] selftests/net: SO_PEERPIDFD_THREAD Andrew Halaney
2026-10-08 5:05 ` Kuniyuki Iwashima
2026-10-05 15:09 ` [PATCH v4 09/10] pidfs: record the coredump on the dumping thread's pid too Andrew Halaney
2026-10-05 15:09 ` [PATCH v4 10/10] selftests/coredump: check the dumping thread's pidfd Andrew Halaney
2026-10-12 9:00 ` Christian Brauner [this message]
2026-10-12 15:59 ` [PATCH v4 00/10] net: support thread-specific pidfds for send and connect Paolo Abeni
2026-10-12 18:14 ` Andrew Halaney
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=20261012-panik-helligkeitsgrad-hackfleisch-c9830fcaf7fc@brauner \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=andrew@amutable.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willemb@google.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
all inboxes | Powered by JetHome®