[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<169051502553.18144.8079815837647562945.git-patchwork-notify@kernel.org>
Date: Fri, 28 Jul 2023 03:30:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Hannes Reinecke <hare@...e.de>
Cc: hch@....de, sagi@...mberg.me, kbusch@...nel.org,
linux-nvme@...ts.infradead.org, kuba@...nel.org, edumazet@...gle.com,
pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCHv9 0/6] net/tls: fixes for NVMe-over-TLS
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 26 Jul 2023 21:15:50 +0200 you wrote:
> Hi all,
>
> here are some small fixes to get NVMe-over-TLS up and running.
> The first set are just minor modifications to have MSG_EOR handled
> for TLS, but the second set implements the ->read_sock() callback
> for tls_sw.
> The ->read_sock() callbacks return -EIO when encountering any TLS
> Alert message, but as that's the default behaviour anyway I guess
> we can get away with it.
>
> [...]
Here is the summary with links:
- [1/6] net/tls: handle MSG_EOR for tls_sw TX flow
https://git.kernel.org/netdev/net-next/c/e22e358bbeb3
- [2/6] net/tls: handle MSG_EOR for tls_device TX flow
https://git.kernel.org/netdev/net-next/c/c004b0e00c94
- [3/6] selftests/net/tls: add test for MSG_EOR
https://git.kernel.org/netdev/net-next/c/8790c6a4f54d
- [4/6] net/tls: Use tcp_read_sock() instead of ops->read_sock()
https://git.kernel.org/netdev/net-next/c/11863c6d440d
- [5/6] net/tls: split tls_rx_reader_lock
https://git.kernel.org/netdev/net-next/c/f9ae3204fb45
- [6/6] net/tls: implement ->read_sock()
https://git.kernel.org/netdev/net-next/c/662fbcec32f4
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