[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKmqyKOj_vB3dwy2CO2JacL-w6WSm-2HYHuikndsLfYCQvwZNA@mail.gmail.com>
Date: Thu, 13 Nov 2025 12:16:18 +1000
From: Alistair Francis <alistair23@...il.com>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: hare@...nel.org, kernel-tls-handshake@...ts.linux.dev,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-nfs@...r.kernel.org, kbusch@...nel.org, axboe@...nel.dk, hch@....de,
sagi@...mberg.me, kch@...dia.com, hare@...e.de,
Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH v5 4/6] net/handshake: Support KeyUpdate message types
On Thu, Nov 13, 2025 at 1:49 AM Chuck Lever <chuck.lever@...cle.com> wrote:
>
> On 11/11/25 11:27 PM, alistair23@...il.com wrote:
> > From: Alistair Francis <alistair.francis@....com>
> >
> > When reporting the msg-type to userspace let's also support reporting
> > KeyUpdate events. This supports reporting a client/server event and if
> > the other side requested a KeyUpdateRequest.
> >
> > Link: https://datatracker.ietf.org/doc/html/rfc8446#section-4.6.3
> > Signed-off-by: Alistair Francis <alistair.francis@....com>
>
> I was not able to apply this to either v6.18-rc5, nfsd-testing, or
> netdev-next, so I can't adequately review or test it. Is this series
> available on a public git branch?
You might have missed Hanne's "nvme-tcp: Implement recvmsg() receive
flow" patch that is required, it's mentioned in the cover letter.
You can find this series, Hanne's patch, a few other patches that
are all on list and some extra patches I'm using for testing and debugging here:
https://github.com/alistair23/linux/tree/alistair/tls-keyupdate
Just remove the top commits from that branch to get just this series
Alistair
>
>
> --
> Chuck Lever
Powered by blists - more mailing lists