From: patchwork-bot+netdevbpf@kernel.org
To: Maximilian Immanuel Brandtner <maxbr@linux.ibm.com>
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, svens@linux.ibm.com,
brueckner@linux.ibm.com
Subject: Re: [PATCH net v2] tls: fix RX desync on overlapping skbs
Date: Tue, 18 Aug 2026 01:20:05 +0000 [thread overview]
Message-ID: <178701600540.1817778.12632713486409028409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813121337.3300688-1-maxbr@linux.ibm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Aug 2026 14:09:44 +0200 you wrote:
> The TCP receive queue can hold adjacent skbs whose sequence ranges
> overlap. The tls fast-path reads the record header with skb_copy_bits()
> by byte offset, which assumes skbs do not overlap, so a header split
> across the overlap is misread and the connection aborts
> (-EMSGSIZE/-EINVAL). tls_strp_check_queue_ok() detects such overlaps but
> only ran after the header was parsed, never covering the header itself.
>
> [...]
Here is the summary with links:
- [net,v2] tls: fix RX desync on overlapping skbs
https://git.kernel.org/netdev/net/c/9466ef3ec972
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-08-18 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 12:09 [PATCH net v2] tls: fix RX desync on overlapping skbs Maximilian Immanuel Brandtner
2026-08-14 18:21 ` Maximilian Immanuel Brandtner
2026-08-18 1:20 ` 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=178701600540.1817778.12632713486409028409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brueckner@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maxbr@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=svens@linux.ibm.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