From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
bpf@vger.kernel.org, jakub@cloudflare.com,
john.fastabend@gmail.com, sd@queasysnail.net
Subject: Re: [PATCH net-next 0/5] tls: reject the combination of TLS and sockmap
Date: Tue, 16 Jun 2026 16:10:12 +0000 [thread overview]
Message-ID: <178162621239.1143794.13386729126363922107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260614014102.461064-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 13 Jun 2026 18:40:55 -0700 you wrote:
> There are no known TLS+sockmap users and it has some known
> hard to solve bugs. Let's reject this configuration as we
> discussed a number of times.
>
> Jakub Kicinski (5):
> tls: reject the combination of TLS and sockmap
> tls: remove dead sockmap (psock) handling from the SW path
> selftests/bpf: remove sockmap + ktls tests
> selftests/bpf: drop the unused kTLS program from test_sockmap
> selftests/bpf: test that TLS crypto is rejected on a sockmap socket
>
> [...]
Here is the summary with links:
- [net-next,1/5] tls: reject the combination of TLS and sockmap
https://git.kernel.org/netdev/net-next/c/460e6486617c
- [net-next,2/5] tls: remove dead sockmap (psock) handling from the SW path
https://git.kernel.org/netdev/net-next/c/79511603a65b
- [net-next,3/5] selftests/bpf: remove sockmap + ktls tests
https://git.kernel.org/netdev/net-next/c/faf89584e436
- [net-next,4/5] selftests/bpf: drop the unused kTLS program from test_sockmap
https://git.kernel.org/netdev/net-next/c/6af8971d910e
- [net-next,5/5] selftests/bpf: test that TLS crypto is rejected on a sockmap socket
https://git.kernel.org/netdev/net-next/c/5949a7cf11e6
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-06-16 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 1:40 [PATCH net-next 0/5] tls: reject the combination of TLS and sockmap Jakub Kicinski
2026-06-14 1:40 ` [PATCH net-next 1/5] " Jakub Kicinski
2026-06-14 8:09 ` Paolo Abeni
2026-06-14 19:12 ` Jakub Sitnicki
2026-06-15 18:20 ` Jakub Kicinski
2026-06-15 18:45 ` Jakub Sitnicki
2026-06-15 22:00 ` Sabrina Dubroca
2026-06-14 1:40 ` [PATCH net-next 2/5] tls: remove dead sockmap (psock) handling from the SW path Jakub Kicinski
2026-06-15 14:55 ` Jakub Sitnicki
2026-06-15 22:20 ` Sabrina Dubroca
2026-06-14 1:40 ` [PATCH net-next 3/5] selftests/bpf: remove sockmap + ktls tests Jakub Kicinski
2026-06-16 10:04 ` Jakub Sitnicki
2026-06-14 1:40 ` [PATCH net-next 4/5] selftests/bpf: drop the unused kTLS program from test_sockmap Jakub Kicinski
2026-06-14 1:41 ` [PATCH net-next 5/5] selftests/bpf: test that TLS crypto is rejected on a sockmap socket Jakub Kicinski
2026-06-16 16:10 ` 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=178162621239.1143794.13386729126363922107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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