From: Sabrina Dubroca <sd@queasysnail.net>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 6.12.y 1/2] selftests: tls: add rekey tests
Date: Wed, 19 Aug 2026 17:19:24 +0200 [thread overview]
Message-ID: <aoXJfMDP52O9vZVY@krikkit> (raw)
In-Reply-To: <20260819113944.3620902-1-sashal@kernel.org>
2026-08-19, 07:39:43 -0400, Sasha Levin wrote:
> From: Sabrina Dubroca <sd@queasysnail.net>
>
> [ Upstream commit 555f0edb9ff043196655a5b7cc65f67dfd05b530 ]
>
> Test the kernel's ability to:
> - update the key (but not the version or cipher), only for TLS1.3
> - pause decryption after receiving a KeyUpdate message, until a new
> RX key has been provided
> - reflect the pause/non-readable socket in poll()
>
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Stable-dep-of: 1c8629651cb5 ("tls: rx: restore msg_iter before TLS 1.3 optimistic retry")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> tools/testing/selftests/net/tls.c | 458 ++++++++++++++++++++++++++++++
> 1 file changed, 458 insertions(+)
All of those rekey tests are going to fail if you don't take the rekey
implementation as well (which I hope isn't getting backported to any
stable kernels). You probably don't want that.
--
Sabrina
next prev parent reply other threads:[~2026-08-19 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 12:48 FAILED: patch "[PATCH] tls: rx: restore msg_iter before TLS 1.3 optimistic retry" failed to apply to 6.12-stable tree gregkh
2026-08-19 11:39 ` [PATCH 6.12.y 1/2] selftests: tls: add rekey tests Sasha Levin
2026-08-19 11:39 ` [PATCH 6.12.y 2/2] tls: rx: restore msg_iter before TLS 1.3 optimistic retry Sasha Levin
2026-08-19 15:19 ` Sabrina Dubroca [this message]
2026-08-21 16:51 ` [PATCH 6.12.y 1/2] selftests: tls: add rekey tests Sasha Levin
2026-08-21 20:10 ` Sabrina Dubroca
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=aoXJfMDP52O9vZVY@krikkit \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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