[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bb9d7860505a852b6349581e266f53c9752df7ad.camel@wdc.com>
Date: Tue, 14 Oct 2025 10:19:32 +0000
From: Wilfred Mallawa <wilfred.mallawa@....com>
To: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "corbet@....net" <corbet@....net>, "davem@...emloft.net"
<davem@...emloft.net>, "john.fastabend@...il.com" <john.fastabend@...il.com>,
"sd@...asysnail.net" <sd@...asysnail.net>, "shuah@...nel.org"
<shuah@...nel.org>, "kuba@...nel.org" <kuba@...nel.org>, "horms@...nel.org"
<horms@...nel.org>, "edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>
Subject: Re: [PATCH net-next v5 1/2] net/tls: support setting the maximum
payload size
On Tue, 2025-10-14 at 15:18 +1000, Wilfred Mallawa wrote:
> +static int do_tls_setsockopt_tx_payload_len(struct sock *sk,
> sockptr_t optval,
> + unsigned int optlen)
> +{
> + struct tls_context *ctx = tls_get_ctx(sk);
> + struct tls_sw_context_tx *sw_ctx = tls_sw_ctx_tx(ctx);
> + u16 value;
> +
> + if (sw_ctx->open_rec)
> + return -EBUSY;
Looks like syzbot found a bug here, sw_ctx can be NULL. Will fixup for
V5.
Wilfred
Powered by blists - more mailing lists