From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
cratiu@nvidia.com, gal@nvidia.com, lkayal@nvidia.com,
leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, maord@nvidia.com, mbloch@nvidia.com,
saeedm@nvidia.com
Subject: Re: [PATCH net] net/mlx5: E-Switch, prevent mc_list repopulation during vport disable
Date: Sat, 05 Sep 2026 20:30:09 +0000 [thread overview]
Message-ID: <178864020915.1345393.18226763979280316717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902193854.3669035-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 22:38:54 +0300 you wrote:
> From: Lama Kayal <lkayal@nvidia.com>
>
> In mlx5_esw_vport_disable(), move esw_apply_vport_rx_mode() ahead
> of esw_vport_change_handle_locked() so vport->allmulti_rule is
> NULL before the change handler observes it.
>
> During FW-fatal recovery the disable runs while dev->state ==
> INTERNAL_ERROR. The promisc query inside esw_update_vport_rx_mode()
> fails and returns early, leaving vport->allmulti_rule intact, so
> esw_update_vport_mc_promisc() runs and adds MLX5_ACTION_ADD entries
> to vport->mc_list whose flow rules are then installed in the FDB
> by esw_add_mc_addr(). esw_destroy_legacy_table() tears down the
> FDB with those refs still held, corrupting the sub-tree and
> leaving dangling flow_rule pointers in vport->mc_list.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: E-Switch, prevent mc_list repopulation during vport disable
https://git.kernel.org/netdev/net/c/c0c6f4ba8a37
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-09-05 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:38 [PATCH net] net/mlx5: E-Switch, prevent mc_list repopulation during vport disable Tariq Toukan
2026-09-05 20:30 ` 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=178864020915.1345393.18226763979280316717.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkayal@nvidia.com \
--cc=maord@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.