From: patchwork-bot+netdevbpf@kernel.org
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, leon@kernel.org, dsahern@kernel.org,
arnd@arndb.de, keescook@chromium.org, brauner@kernel.org,
kuniyu@amazon.com, mzxreary@0pointer.de, bluca@debian.org,
daniel@iogearbox.net, sdf@google.com
Subject: Re: [PATCH net-next v7 0/4] Add SCM_PIDFD and SO_PEERPIDFD
Date: Mon, 12 Jun 2023 09:50:20 +0000 [thread overview]
Message-ID: <168656342089.25012.9925385632760123942.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230608202628.837772-1-aleksandr.mikhalitsyn@canonical.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 8 Jun 2023 22:26:24 +0200 you wrote:
> 1. Implement SCM_PIDFD, a new type of CMSG type analogical to SCM_CREDENTIALS,
> but it contains pidfd instead of plain pid, which allows programmers not
> to care about PID reuse problem.
>
> 2. Add SO_PEERPIDFD which allows to get pidfd of peer socket holder pidfd.
> This thing is direct analog of SO_PEERCRED which allows to get plain PID.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/4] scm: add SO_PASSPIDFD and SCM_PIDFD
https://git.kernel.org/netdev/net-next/c/5e2ff6704a27
- [net-next,v7,2/4] net: core: add getsockopt SO_PEERPIDFD
https://git.kernel.org/netdev/net-next/c/7b26952a91cf
- [net-next,v7,3/4] selftests: net: add SCM_PIDFD / SO_PEERPIDFD test
https://git.kernel.org/netdev/net-next/c/ec80f488252b
- [net-next,v7,4/4] af_unix: Kconfig: make CONFIG_UNIX bool
https://git.kernel.org/netdev/net-next/c/97154bcf4d1b
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:[~2023-06-12 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 20:26 [PATCH net-next v7 0/4] Add SCM_PIDFD and SO_PEERPIDFD Alexander Mikhalitsyn
2023-06-08 20:26 ` [PATCH net-next v7 1/4] scm: add SO_PASSPIDFD and SCM_PIDFD Alexander Mikhalitsyn
2023-06-12 9:19 ` Eric Dumazet
2023-06-12 9:26 ` Aleksandr Mikhalitsyn
2023-09-01 20:05 ` Heiko Carstens
2023-09-01 20:33 ` Kuniyuki Iwashima
2023-09-01 20:51 ` Heiko Carstens
2023-09-01 20:56 ` Kuniyuki Iwashima
2023-09-01 21:11 ` Aleksandr Mikhalitsyn
2023-06-08 20:26 ` [PATCH net-next v7 2/4] net: core: add getsockopt SO_PEERPIDFD Alexander Mikhalitsyn
2023-06-12 9:22 ` Eric Dumazet
2023-06-08 20:26 ` [PATCH net-next v7 3/4] selftests: net: add SCM_PIDFD / SO_PEERPIDFD test Alexander Mikhalitsyn
2023-06-08 20:26 ` [PATCH net-next v7 4/4] af_unix: Kconfig: make CONFIG_UNIX bool Alexander Mikhalitsyn
2023-06-09 8:06 ` Christian Brauner
2023-06-12 9:25 ` Eric Dumazet
2023-06-12 9:50 ` 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=168656342089.25012.9925385632760123942.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=arnd@arndb.de \
--cc=bluca@debian.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@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;
as well as URLs for NNTP newsgroup(s).