[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250815100218.4a492986@kernel.org>
Date: Fri, 15 Aug 2025 10:02:18 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: alistair23@...il.com
Cc: chuck.lever@...cle.com, 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, Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH 4/8] tls: Allow callers to clear errors
On Fri, 15 Aug 2025 15:02:06 +1000 alistair23@...il.com wrote:
> As part of supporting KeyUpdate we are going to pass errors up to the
> callers of TLS to indaicate a KeyUpdate. Those layers will need to handle
> the KeyUpdate and as part of that clear the error.
> +static inline void tls_clear_err(struct sock *sk)
> +{
> + WRITE_ONCE(sk->sk_err, 0);
> + /* Paired with smp_rmb() in tcp_poll() */
> + smp_wmb();
Please explain how the key error ends up recorded on the socket.
Powered by blists - more mailing lists