From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, davejwatson@fb.com,
borisp@nvidia.com, john.fastabend@gmail.com,
daniel@iogearbox.net, vakul.garg@nxp.com, willemb@google.com,
vfedorenko@novek.ru
Subject: Re: [PATCH net 0/9] tls: splice_read fixes
Date: Fri, 26 Nov 2021 03:40:10 +0000 [thread overview]
Message-ID: <163789801005.11827.6777069980777661670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211124232557.2039757-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 24 Nov 2021 15:25:48 -0800 you wrote:
> As I work my way to unlocked and zero-copy TLS Rx the obvious bugs
> in the splice_read implementation get harder and harder to ignore.
> This is to say the fixes here are discovered by code inspection,
> I'm not aware of anyone actually using splice_read.
>
> Jakub Kicinski (9):
> selftests: tls: add helper for creating sock pairs
> selftests: tls: factor out cmsg send/receive
> selftests: tls: add tests for handling of bad records
> tls: splice_read: fix record type check
> selftests: tls: test splicing cmsgs
> tls: splice_read: fix accessing pre-processed records
> selftests: tls: test splicing decrypted records
> tls: fix replacing proto_ops
> selftests: tls: test for correct proto_ops
>
> [...]
Here is the summary with links:
- [net,1/9] selftests: tls: add helper for creating sock pairs
https://git.kernel.org/netdev/net/c/a125f91fe783
- [net,2/9] selftests: tls: factor out cmsg send/receive
https://git.kernel.org/netdev/net/c/31180adb0bed
- [net,3/9] selftests: tls: add tests for handling of bad records
https://git.kernel.org/netdev/net/c/ef0fc0b3cc2b
- [net,4/9] tls: splice_read: fix record type check
https://git.kernel.org/netdev/net/c/520493f66f68
- [net,5/9] selftests: tls: test splicing cmsgs
https://git.kernel.org/netdev/net/c/d87d67fd61ef
- [net,6/9] tls: splice_read: fix accessing pre-processed records
https://git.kernel.org/netdev/net/c/e062fe99cccd
- [net,7/9] selftests: tls: test splicing decrypted records
https://git.kernel.org/netdev/net/c/274af0f9e279
- [net,8/9] tls: fix replacing proto_ops
https://git.kernel.org/netdev/net/c/f3911f73f51d
- [net,9/9] selftests: tls: test for correct proto_ops
https://git.kernel.org/netdev/net/c/f884a3426291
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:[~2021-11-26 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 23:25 [PATCH net 0/9] tls: splice_read fixes Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 1/9] selftests: tls: add helper for creating sock pairs Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 2/9] selftests: tls: factor out cmsg send/receive Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 3/9] selftests: tls: add tests for handling of bad records Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 4/9] tls: splice_read: fix record type check Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 5/9] selftests: tls: test splicing cmsgs Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 6/9] tls: splice_read: fix accessing pre-processed records Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 7/9] selftests: tls: test splicing decrypted records Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 8/9] tls: fix replacing proto_ops Jakub Kicinski
2021-11-24 23:25 ` [PATCH net 9/9] selftests: tls: test for correct proto_ops Jakub Kicinski
2021-11-26 3:40 ` 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=163789801005.11827.6777069980777661670.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=vakul.garg@nxp.com \
--cc=vfedorenko@novek.ru \
--cc=willemb@google.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 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.