[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170855462906.28356.14505768197240352814.git-patchwork-notify@kernel.org>
Date: Wed, 21 Feb 2024 22:30:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Sabrina Dubroca <sd@...asysnail.net>
Cc: netdev@...r.kernel.org, borisp@...dia.com, john.fastabend@...il.com,
kuba@...nel.org, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
shuah@...nel.org, vakul.garg@....com, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net 0/5] tls: fixes for record type handling with PEEK
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 15 Feb 2024 17:17:28 +0100 you wrote:
> There are multiple bugs in tls_sw_recvmsg's handling of record types
> when MSG_PEEK flag is used, which can lead to incorrectly merging two
> records:
> - consecutive non-DATA records shouldn't be merged, even if they're
> the same type (partly handled by the test at the end of the main
> loop)
> - records of the same type (even DATA) shouldn't be merged if one
> record of a different type comes in between
>
> [...]
Here is the summary with links:
- [net,1/5] tls: break out of main loop when PEEK gets a non-data record
https://git.kernel.org/netdev/net/c/10f41d0710fc
- [net,2/5] tls: stop recv() if initial process_rx_list gave us non-DATA
https://git.kernel.org/netdev/net/c/fdfbaec5923d
- [net,3/5] tls: don't skip over different type records from the rx_list
https://git.kernel.org/netdev/net/c/ec823bf3a479
- [net,4/5] selftests: tls: add test for merging of same-type control messages
https://git.kernel.org/netdev/net/c/7b2a4c2a623a
- [net,5/5] selftests: tls: add test for peeking past a record of a different type
https://git.kernel.org/netdev/net/c/2bf6172632e1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists