mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chuck Lever" <cel@kernel.org>
To: "Sabrina Dubroca" <sd@queasysnail.net>,
	"Jakub Kicinski" <kuba@kernel.org>
Cc: "Qingfang Deng" <qingfang.deng@linux.dev>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Dave Watson" <davejwatson@fb.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tls: skip empty data records in tls_sw_splice_read()
Date: Wed, 30 Sep 2026 07:57:46 -0700	[thread overview]
Message-ID: <eb175a90-58d9-4cfc-898a-8083633451cc@app.fastmail.com> (raw)
In-Reply-To: <ar0iBIUzHhZijRem@krikkit>



On Wed, Sep 30, 2026, at 7:51 AM, Sabrina Dubroca wrote:
> 2026-09-30, 06:45:23 -0700, Chuck Lever wrote:
>> 
>> 
>> On Wed, Sep 30, 2026, at 2:47 AM, Sabrina Dubroca wrote:

>> > Let's see if he has the time/interest to continue work on this (since
>> > he didn't send a v2, I'm guessing not).
>> >
>> > Chuck, do you want to pick up that TLS fixes series again, or would
>> > you rather let Qingfang finish off the "splice vs empty record"
>> > patch+selftest based on what you had sent?
>> 
>> History: I stopped working on that since Jakub seemed to think the
>> fixes were not worth the trouble, and my objective is to get kTLS
>> and its kernel consumers in shape to support KeyUpdate.
>
> I /think/ he meant that some patches in that series were ready to go
> in and worthy of being merged quickly, while others were less urgent
> and less ready, and could be finished later on (but not necessarily
> that the issues shouldn't be fixed at all).

I recall the use of the word "doubtful". I'm happy to continue to
pursue them, but I don't want to waste reviewer/maintainer time.


> But I guess we could just ask him.

Agreed, I probably misread his comment.


-- 
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)

      reply	other threads:[~2026-09-30 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  5:26 Qingfang Deng
2026-09-30  5:29 ` netdev-bot+sinfo
2026-09-30  5:49   ` Qingfang Deng
2026-09-30  9:13 ` Sabrina Dubroca
2026-09-30  9:24   ` Qingfang Deng
2026-09-30  9:47     ` Sabrina Dubroca
2026-09-30 13:45       ` Chuck Lever
2026-09-30 14:51         ` Sabrina Dubroca
2026-09-30 14:57           ` Chuck Lever [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=eb175a90-58d9-4cfc-898a-8083633451cc@app.fastmail.com \
    --to=cel@kernel.org \
    --cc=davejwatson@fb.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qingfang.deng@linux.dev \
    --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

all inboxes | Powered by JetHome®