From: patchwork-bot+netdevbpf@kernel.org
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com,
kuba@kernel.org, sd@queasysnail.net, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
borisp@mellanox.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] tls: keep TX and RX hardware offload on the same device
Date: Wed, 28 Oct 2026 08:50:04 +0000 [thread overview]
Message-ID: <179317740457.586826.13676893511407745921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020214500.972308-1-rjethwani@purestorage.com>
Hello:
This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Tue, 20 Oct 2026 15:44:59 -0600 you wrote:
> After TX is offloaded on device A, a route change, or a change in the
> usable-slave set of an 802.3ad or balance-xor (layer3+4) bond, can make
> RX setup program device B. tls_device_attach() sees the existing TLS
> destructor and keeps ctx->netdev pointing at A. The RX driver state on B
> is then untracked: tls_dev_resync() and tls_dev_del() are invoked on A
> for a context it never created, and neither socket close nor
> NETDEV_DOWN on B calls tls_dev_del() for B, so the driver context leaks.
> The reverse setup order has the same problem.
>
> [...]
Here is the summary with links:
- [net,v2] tls: keep TX and RX hardware offload on the same device
https://git.kernel.org/netdev/net/c/1c8a70075235
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-28 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:44 [PATCH net v2] tls: keep TX and RX hardware offload on the same device Rishikesh Jethwani
2026-10-20 21:49 ` netdev-bot+sinfo
2026-10-21 20:37 ` Rishikesh Jethwani
2026-10-24 22:02 ` netdev-bot+sashiko
2026-10-27 18:06 ` Rishikesh Jethwani
2026-10-28 8:50 ` 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=179317740457.586826.13676893511407745921.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=borisp@mellanox.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rjethwani@purestorage.com \
--cc=sd@queasysnail.net \
--cc=skhan@linuxfoundation.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