From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
To: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"sd@queasysnail.net" <sd@queasysnail.net>,
"shuah@kernel.org" <shuah@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>
Subject: Re: [PATCH net-next v5 1/2] net/tls: support setting the maximum payload size
Date: Tue, 14 Oct 2025 10:19:32 +0000 [thread overview]
Message-ID: <bb9d7860505a852b6349581e266f53c9752df7ad.camel@wdc.com> (raw)
In-Reply-To: <20251014051825.1084403-2-wilfred.opensource@gmail.com>
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
prev parent reply other threads:[~2025-10-14 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 5:18 [PATCH net-next v5 1/2] net/tls: support setting the maximum payload size Wilfred Mallawa
2025-10-14 5:18 ` [PATCH net-next v5 2/2] selftests: tls: add tls record_size_limit test Wilfred Mallawa
2025-10-14 10:04 ` [syzbot ci] Re: net/tls: support setting the maximum payload size syzbot ci
2025-10-14 10:19 ` Wilfred Mallawa [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=bb9d7860505a852b6349581e266f53c9752df7ad.camel@wdc.com \
--to=wilfred.mallawa@wdc.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).