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, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, saeedm@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH net V2] net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock
Date: Fri, 31 Jul 2026 00:00:13 +0000 [thread overview]
Message-ID: <178545601313.49120.11958619412514428271.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260728044338.2271143-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Jul 2026 07:43:38 +0300 you wrote:
> From: Shay Drory <shayd@nvidia.com>
>
> In case __mlx5e_add_fdb_flow() fails in lower levels, the flow is
> deleted via mlx5e_tc_del_flow(), and mlx5e_tc_del_flow() is acquiring
> ESW devcom lock without condition. In addition, in case of peer_flow,
> __mlx5e_add_fdb_flow() is called while holding ESW devcom comp lock.
> This results in an AA deadlock.
>
> [...]
Here is the summary with links:
- [net,V2] net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock
https://git.kernel.org/netdev/net/c/6ddfba2ea98d
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-07-31 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 4:43 [PATCH net V2] net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock Tariq Toukan
2026-07-31 0:00 ` 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=178545601313.49120.11958619412514428271.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=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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.