From: patchwork-bot+netdevbpf@kernel.org
To: Christian Brauner <brauner@kernel.org>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, kuniyu@google.com,
alexander@mihalicyn.com, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
sashiko-bot@kernel.org
Subject: Re: [PATCH net 0/2] net: fix a pidfd leak with a short SO_PEERPIDFD optlen
Date: Sat, 21 Nov 2026 19:30:06 +0000 [thread overview]
Message-ID: <179528940603.1145636.16413757332346392828.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261117-work-net-peerpidfd_short_optlen-v1-0-a93f56288501@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Nov 2026 16:25:29 +0100 you wrote:
> SO_PEERPIDFD caps optlen at sizeof(int) but never rejects a shorter one.
> With an optlen of 0 to 3 getsockopt() still installs a pidfd and copies
> only part of the fd number to userspace, or none of it. The caller can't
> close an fd it doesn't know about, so the pidfd sticks around until the
> process exits.
>
> That's been the case since SO_PEERPIDFD went in for v6.5. When I moved
> the code into a helper for SO_PEERPIDFD_THREAD in v7.4-rc1 I kept the
> bug, so the new option has it too.
>
> [...]
Here is the summary with links:
- [net,1/2] net: don't leak pidfds through a short SO_PEERPIDFD optlen
https://git.kernel.org/netdev/net/c/fa827805a629
- [net,2/2] selftests/net: check that a short SO_PEERPIDFD optlen fails
https://git.kernel.org/netdev/net/c/c9b3eb7bfd7f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-21 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 15:25 [PATCH net 0/2] net: fix a pidfd leak with a short SO_PEERPIDFD optlen Christian Brauner
2026-11-17 15:25 ` [PATCH net 1/2] net: don't leak pidfds through " Christian Brauner
2026-11-17 16:39 ` Alexander Mikhalitsyn
2026-11-18 2:15 ` Kuniyuki Iwashima
2026-11-17 15:25 ` [PATCH net 2/2] selftests/net: check that a short SO_PEERPIDFD optlen fails Christian Brauner
2026-11-17 16:39 ` Alexander Mikhalitsyn
2026-11-18 2:17 ` Kuniyuki Iwashima
2026-11-18 12:37 ` [PATCH net 0/2] net: fix a pidfd leak with a short SO_PEERPIDFD optlen Christian Brauner
2026-11-21 19:30 ` patchwork-bot+netdevbpf [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=179528940603.1145636.16413757332346392828.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
/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