From: Sabrina Dubroca <sd@queasysnail.net>
To: Chuck Lever <cel@kernel.org>
Cc: John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
Chuck Lever <chuck.lever@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH net-next v12 6/6] tls: Flush backlog before waiting for a new record
Date: Mon, 8 Jun 2026 00:10:51 +0200 [thread overview]
Message-ID: <aiXsa5zx3u0DUn0l@krikkit> (raw)
In-Reply-To: <20260604-tls-read-sock-v12-6-b114efa6e3e2@oracle.com>
2026-06-04, 13:48:29 -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> While lock_sock is held, incoming TCP segments land on
> sk->sk_backlog rather than sk->sk_receive_queue.
> tls_rx_rec_wait() inspects only sk_receive_queue, so backlog
> data remains invisible. For non-blocking callers (read_sock,
> and recvmsg or splice_read with MSG_DONTWAIT) this causes a
> spurious -EAGAIN. For blocking callers it forces an
> unnecessary sleep/wakeup cycle.
>
> Flush the backlog inside tls_rx_rec_wait() before checking
> sk_receive_queue so the strparser can parse newly-arrived
> segments immediately. On the next loop iteration
> tls_read_flush_backlog() may redundantly flush, but this
> path is cold and the cost is negligible.
>
> Backlog processing can run tcp_reset(), which calls
> tcp_done_with_error() to set sk->sk_err = ECONNRESET and then
> tcp_done() to set sk->sk_shutdown = SHUTDOWN_MASK. The pre-existing
> top-of-loop sk_err check already ran before the flush, so the
> freshly-set error would be masked by the next-line sk_shutdown test
> returning 0 (EOF). Re-check sk_err immediately before the sk_shutdown
> test so a connection abort surfaces as -ECONNRESET rather than a clean
> EOF.
>
> Commit f508262ae9f2 ("tls: Preserve sk_err across recvmsg() when
> data has been copied") gave the top-of-loop sk_err check a
> has_copied split. The recheck applies the same handling: when the
> caller has already copied bytes, sk_err is reported but preserved
> so the error surfaces on the next call; otherwise sock_error()
> consumes it so the error is reported exactly once.
>
> Suggested-by: Sabrina Dubroca <sd@queasysnail.net>
> Link: https://lore.kernel.org/netdev/ahgHgQ84RCc8uYrG@krikkit/
> Reviewed-by: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> net/tls/tls_sw.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Reviewed-by: Sabrina Dubroca <sd@queasysnail.net>
Thanks for your patience with this series, Chuck.
--
Sabrina
prev parent reply other threads:[~2026-06-07 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 17:48 [PATCH net-next v12 0/6] tls: receive-path fixes and clean-ups Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 1/6] tls: Avoid evaluating freed skb in tls_sw_read_sock() loop Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 2/6] tls: Re-present partially-consumed records in tls_sw_read_sock() Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 3/6] tls: Move decrypt-failure abort into tls_rx_one_record() Chuck Lever
2026-06-07 3:42 ` Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 4/6] tls: Factor tls_strp_msg_consume() from tls_strp_msg_done() Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 5/6] tls: Suppress spurious saved_data_ready on all receive paths Chuck Lever
2026-06-04 17:48 ` [PATCH net-next v12 6/6] tls: Flush backlog before waiting for a new record Chuck Lever
2026-06-07 22:10 ` Sabrina Dubroca [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=aiXsa5zx3u0DUn0l@krikkit \
--to=sd@queasysnail.net \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox