Netdev List
 help / color / mirror / Atom feed
From: Rishikesh Jethwani <rjethwani@purestorage.com>
To: netdev@vger.kernel.org
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
	davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
	leon@kernel.org, nils.juenemann@gmail.com,
	Rishikesh Jethwani <rjethwani@purestorage.com>
Subject: [PATCH net 0/1] tls: device: push pending open record on splice EOF
Date: Thu,  9 Jul 2026 16:44:35 -0600	[thread overview]
Message-ID: <20260709224436.1608993-1-rjethwani@purestorage.com> (raw)

Hi all,

  A kTLS socket with device (HW) TX offload can leave its final
  record unsent when sendfile(2) is called with count > bytes-
  remaining in the file and the connection is closed without a
  trailing write. fs/splice.c fires ->splice_eof on the socket in
  this case, and tls_device_splice_eof() pre-patch only pushed
  partially-sent records - a fully-assembled but still-open record
  stayed pending until the next write, which an abrupt close()
  never provides. TLS_SW is unaffected; tls_sw_splice_eof() already
  handles pending open records.

  Report and discussion:
  https://lore.kernel.org/netdev/CAMPsyauZ+jzG9AysO0FWv6ZY0kvCUpjX_U7o=oOjCuOQ87BCgg@mail.gmail.com/

Rishikesh

Rishikesh Jethwani (1):
  tls: device: push pending open record on splice EOF

 net/tls/tls_device.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
2.25.1


             reply	other threads:[~2026-07-09 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 22:44 Rishikesh Jethwani [this message]
2026-07-09 22:44 ` [PATCH 1/1] tls: device: push pending open record on splice EOF Rishikesh Jethwani

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=20260709224436.1608993-1-rjethwani@purestorage.com \
    --to=rjethwani@purestorage.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nils.juenemann@gmail.com \
    --cc=pabeni@redhat.com \
    --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