Re: [PATCH net v2] tls: keep TX and RX hardware offload on the same device

[patchwork-bot+netdevbpf]

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>:

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