From: Simon Horman <horms@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, Boris Pismenny <borisp@nvidia.com>,
John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: tls: add a selftest for wrapping rec_seq
Date: Sat, 19 Oct 2024 09:03:07 +0100 [thread overview]
Message-ID: <20241019080307.GG1697@kernel.org> (raw)
In-Reply-To: <20775fcfd0371422921ee60a42de170c0398ac10.1729244987.git.sd@queasysnail.net>
On Fri, Oct 18, 2024 at 12:55:58PM +0200, Sabrina Dubroca wrote:
> Set the initial rec_seq to 0xffffffffffffffff so that it wraps
> immediately. The send() call should fail with EBADMSG.
>
> A bug in this code was fixed in commit cfaa80c91f6f ("net/tls: do not
> free tls_rec on async operation in bpf_exec_tx_verdict()").
>
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-10-19 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 10:55 [PATCH net-next] selftests: tls: add a selftest for wrapping rec_seq Sabrina Dubroca
2024-10-19 8:03 ` Simon Horman [this message]
2024-10-24 14:20 ` 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=20241019080307.GG1697@kernel.org \
--to=horms@kernel.org \
--cc=borisp@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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;
as well as URLs for NNTP newsgroup(s).