From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: netdev@vger.kernel.org, eadavis@qq.com, kuba@kernel.org,
bpf@vger.kernel.org, borisp@nvidia.com
Subject: Re: [PATCH net v2 0/2] tls fixes for SPLICE with more hint
Date: Sun, 14 Jan 2024 12:20:24 +0000 [thread overview]
Message-ID: <170523482480.13495.3024622886395212564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240113003258.67899-1-john.fastabend@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 Jan 2024 16:32:56 -0800 you wrote:
> Syzbot found a splat where it tried to splice data over a tls socket
> with the more hint and sending greater than the number of frags that
> fit in a msg scatterlist. This resulted in an error where we do not
> correctly send the data when the msg sg is full. The more flag being
> just a hint not a strict contract. This then results in the syzbot
> warning on the next send.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: tls, fix WARNIING in __sk_msg_free
https://git.kernel.org/netdev/net/c/dc9dfc8dc629
- [net,v2,2/2] net: tls, add test to capture error on large splice
https://git.kernel.org/netdev/net/c/034ea1305e65
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:[~2024-01-14 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 0:32 [PATCH net v2 0/2] tls fixes for SPLICE with more hint John Fastabend
2024-01-13 0:32 ` [PATCH net v2 1/2] net: tls, fix WARNIING in __sk_msg_free John Fastabend
2024-01-13 0:32 ` [PATCH net v2 2/2] net: tls, add test to capture error on large splice John Fastabend
2024-01-13 2:45 ` Jakub Kicinski
2024-01-14 12: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=170523482480.13495.3024622886395212564.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=eadavis@qq.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@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