From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
netdev@vger.kernel.org, jeremy.jean@oss.cyber.gouv.fr,
stable@vger.kernel.org
Subject: Re: [PATCH] tls: rx: restore msg_iter before TLS 1.3 optimistic retry
Date: Thu, 06 Aug 2026 16:20:08 +0000 [thread overview]
Message-ID: <178603320838.1362900.14870685122061393780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804125528.2139928-1-Jeremy.Jean@oss.cyber.gouv.fr>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Aug 2026 12:55:28 +0000 you wrote:
> tls_decrypt_sg() advances msg->msg_iter when it maps user pages for
> the optimistic TLS 1.3 zero-copy path. If the decrypted record turns
> out not to be unpadded application data, tls_decrypt_sw() retries into
> a kernel skb, but leaves the iterator advanced.
>
> The subsequent copy from the skb then writes decrypted bytes again at
> a later point in the caller iovecs while recvmsg() reports only the
> post-retry length. A TLS peer can trigger this after the receiver
> enables TLS_RX_EXPECT_NO_PAD.
>
> [...]
Here is the summary with links:
- tls: rx: restore msg_iter before TLS 1.3 optimistic retry
https://git.kernel.org/netdev/net/c/1c8629651cb5
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-06 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 12:55 [PATCH] tls: rx: restore msg_iter before TLS 1.3 optimistic retry Jérémy Jean
2026-08-06 16: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=178603320838.1362900.14870685122061393780.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?SsOpcsOpbXkgSmVhbiA8SmVyZW15LkplYW5Ab3NzLmN5YmVyLmdvdXYuZnI+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=jeremy.jean@oss.cyber.gouv.fr \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.