From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
borisp@nvidia.com, john.fastabend@gmail.com, maximmi@nvidia.com,
tariqt@nvidia.com, vfedorenko@novek.ru,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/4] tls: rx: follow ups to rx work
Date: Tue, 26 Jul 2022 20:15:20 -0700 [thread overview]
Message-ID: <20220727031524.358216-1-kuba@kernel.org> (raw)
A selection of unrelated changes. First some selftest polishing.
Next a change to rcvtimeo handling for locking based on an exchange
with Eric. Follow up to Paolo's comments from yesterday. Last but
not least a fix to a false positive warning, turns out I've been
testing with DEBUG_NET=n this whole time.
Jakub Kicinski (4):
selftests: tls: handful of memrnd() and length checks
tls: rx: don't consider sock_rcvtimeo() cumulative
tls: strp: rename and multithread the workqueue
tls: rx: fix the false positive warning
net/tls/tls_strp.c | 2 +-
net/tls/tls_sw.c | 39 ++++++++++++++++---------------
tools/testing/selftests/net/tls.c | 26 ++++++++++++++-------
3 files changed, 38 insertions(+), 29 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-27 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 3:15 Jakub Kicinski [this message]
2022-07-27 3:15 ` [PATCH net-next 1/4] selftests: tls: handful of memrnd() and length checks Jakub Kicinski
2022-07-27 3:15 ` [PATCH net-next 2/4] tls: rx: don't consider sock_rcvtimeo() cumulative Jakub Kicinski
2022-07-28 13:50 ` Paolo Abeni
2022-07-28 15:42 ` Jakub Kicinski
2022-07-28 15:47 ` Eric Dumazet
2022-07-28 20:04 ` Paolo Abeni
2022-07-27 3:15 ` [PATCH net-next 3/4] tls: strp: rename and multithread the workqueue Jakub Kicinski
2022-07-27 3:15 ` [PATCH net-next 4/4] tls: rx: fix the false positive warning Jakub Kicinski
2022-07-29 5:00 ` [PATCH net-next 0/4] tls: rx: follow ups to rx work patchwork-bot+netdevbpf
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=20220727031524.358216-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
--cc=vfedorenko@novek.ru \
/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.