From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: John Fastabend <john.fastabend@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Dave Watson <davejwatson@fb.com>, Shuah Khan <shuah@kernel.org>,
Qingfang Deng <qingfang.deng@linux.dev>,
Eric Dumazet <edumazet@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
sashiko-bot <sashiko-bot@kernel.org>,
sashiko-bot <netdev-bot+sashiko@kernel.org>
Subject: Re: [PATCH net-next v6 0/9] net/tls: Receive-path fixes for zero-length data records
Date: Mon, 26 Oct 2026 15:37:48 -0700 [thread overview]
Message-ID: <20261026153748.29911bae@kernel.org> (raw)
In-Reply-To: <20261019-tls-follow-on-v6-0-ab01c4ecca0c@kernel.org>
On Mon, 19 Oct 2026 12:55:16 -0400 Chuck Lever wrote:
> Commit 3be28e2c9cd0 ("net/tls: Consume empty data records in
> tls_sw_read_sock()") fixed one reader. TLS 1.2 and TLS 1.3 both
> permit a zero-length application_data record as a traffic-analysis
> countermeasure (RFC 5246, Section 6.2.1; RFC 8446, Section 5.1), so
> a peer that pads its stream emits them by design. The other two
> software readers still mishandle them. splice(2) reports an empty
> record as EOF, and the caller tears down a connection that is still
> live. recvmsg(2) makes no progress on one, so a peer that streams
> them holds the caller in the kernel past SIGKILL. With MSG_PEEK or
> async decryption, each record is also queued on rx_list, which
> grows without bound.
The shape of this series is still quite confusing to me.
Let me take over a little bit so that we make some progress
(while retaining your authorship where possible).
next prev parent reply other threads:[~2026-10-26 22:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:55 [PATCH net-next v6 0/9] net/tls: Receive-path fixes for zero-length data records Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 1/9] tls: Bound consecutive no-data records in tls_sw_read_sock() Chuck Lever
2026-10-22 19:57 ` netdev-bot+sashiko
2026-10-23 15:15 ` Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 2/9] tls: Check for a pending signal after an empty record Chuck Lever
2026-10-22 19:57 ` netdev-bot+sashiko
2026-10-23 15:18 ` Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 3/9] tls: Honor O_NONBLOCK in tls_sw_splice_read() Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 4/9] tls: Consume empty data records " Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 5/9] tls: Consume empty data records in tls_sw_recvmsg() Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 6/9] tls: Return copied data ahead of a run of empty records Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 7/9] selftests: tls: Skip the zero_len tests when TLS is unavailable Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 8/9] selftests: tls: Extend coverage for zero-length records Chuck Lever
2026-10-22 19:57 ` netdev-bot+sashiko
2026-10-23 15:20 ` Chuck Lever
2026-10-19 16:55 ` [PATCH net-next v6 9/9] selftests: tls: Cover splice on a nonblocking socket Chuck Lever
2026-10-26 22:37 ` Jakub Kicinski [this message]
2026-10-27 13:01 ` [PATCH net-next v6 0/9] net/tls: Receive-path fixes for zero-length data records Chuck Lever
2026-10-27 22:00 ` Jakub Kicinski
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=20261026153748.29911bae@kernel.org \
--to=kuba@kernel.org \
--cc=cel@kernel.org \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@linux.dev \
--cc=sashiko-bot@kernel.org \
--cc=sd@queasysnail.net \
--cc=shuah@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 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.