mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, sd@queasysnail.net,
	john.fastabend@gmail.com, kuba@kernel.org, davem@davemloft.net,
	edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
	wilfred.mallawa@wdc.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] tls: fix the open record check in the max payload size setsockopt
Date: Fri, 23 Oct 2026 21:20:04 +0000	[thread overview]
Message-ID: <179279040457.1276597.15193164800463217600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020121240.29082-1-jiayuan.chen@linux.dev>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 20 Oct 2026 20:12:39 +0800 you wrote:
> do_tls_setsockopt_tx_payload_len() refuses to resize records while one is
> open, but the check is broken in two ways.
> 
> It reaches for the open record through tls_sw_ctx_tx(), an unchecked cast
> of ctx->priv_ctx_tx.  Under device offload that pointer is a
> tls_offload_context_tx, so the check reads a field of the wrong struct: it
> returns EBUSY on whatever happens to be there, and never sees the record
> that really is open.  Dispatch on tx_conf.
> 
> [...]

Here is the summary with links:
  - [net,v3] tls: fix the open record check in the max payload size setsockopt
    https://git.kernel.org/netdev/net/c/ed642349d87d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-23 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 12:12 Jiayuan Chen
2026-10-20 12:18 ` netdev-bot+sinfo
2026-10-23 21:09 ` Jakub Kicinski
2026-10-23 21:20 ` patchwork-bot+netdevbpf [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=179279040457.1276597.15193164800463217600.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --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=sd@queasysnail.net \
    --cc=wilfred.mallawa@wdc.com \
    /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®