From: patchwork-bot+netdevbpf@kernel.org
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, jiayuan.chen@linux.dev,
stable@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
ncardwell@google.com, kuniyu@google.com,
john.fastabend@gmail.com, sd@queasysnail.net, davejwatson@fb.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v8] kcm: reject TLS on attached TCP sockets
Date: Sat, 21 Nov 2026 23:44:23 +0000 [thread overview]
Message-ID: <179530466302.1212208.15645522376520311508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116190111.3317976-1-rjethwani@purestorage.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Nov 2026 12:01:08 -0700 you wrote:
> Neither kcm_attach() nor tls_init() rejects the other, so KCM and kTLS RX
> can be stacked on the same TCP socket in either order. This breaks in
> several ways:
>
> - KCM calls read_sock() from its receive callback in atomic context.
> With kTLS RX this reaches tls_sw_read_sock(), which can sleep.
> - Before tls_sw_read_sock() existed, read_sock was tcp_read_sock(), so
> KCM consumed raw ciphertext from the receive queue that TLS parses.
> - Both install socket callbacks. kcm_unattach() restores the pre-KCM
> sk_data_ready over tls_data_ready, so TLS RX stops getting notified.
>
> [...]
Here is the summary with links:
- [net,v8] kcm: reject TLS on attached TCP sockets
https://git.kernel.org/netdev/net/c/746dbdc5fa60
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 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 19:01 Rishikesh Jethwani
2026-11-16 19:02 ` netdev-bot+sinfo
2026-11-16 19:05 ` Rishikesh Jethwani
2026-11-21 23:44 ` 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=179530466302.1212208.15645522376520311508.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rjethwani@purestorage.com \
--cc=sd@queasysnail.net \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®