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, kees@kernel.org, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, saeedm@nvidia.com, ychemla@nvidia.com
Subject: Re: [PATCH net] net/mlx5: E-Switch, fix zero num_dest in prio_tag egress vlan rule
Date: Thu, 23 Jul 2026 15:30:18 +0000 [thread overview]
Message-ID: <178482061816.2321119.15008750481814720639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260717073306.1242399-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 17 Jul 2026 10:33:06 +0300 you wrote:
> From: Yael Chemla <ychemla@nvidia.com>
>
> esw_egress_acl_vlan_create() hardcodes num_dest=0 in its
> mlx5_add_flow_rules() call. When invoked from the non-bond path
> fwd_dest is NULL and num_dest=0 is correct. When invoked from
> esw_acl_egress_ofld_rules_create() during a bond event, fwd_dest is
> non-NULL and flow_act.action carries MLX5_FLOW_CONTEXT_ACTION_FWD_DEST,
> but _mlx5_add_flow_rules() rejects a non-NULL dest pointer paired with
> dest_num<=0 and returns -EINVAL. The error propagates as
> "configure slave vport egress fwd, err(-22)". The passive vport's egress
> ACL table ends up with its flow groups allocated but no FTEs, so
> prio-tagged packets are not popped and bond failover is broken on
> prio_tag_required devices.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: E-Switch, fix zero num_dest in prio_tag egress vlan rule
https://git.kernel.org/netdev/net/c/d12956d083eb
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-23 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 7:33 [PATCH net] net/mlx5: E-Switch, fix zero num_dest in prio_tag egress vlan rule Tariq Toukan
2026-07-23 15: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=178482061816.2321119.15008750481814720639.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=kees@kernel.org \
--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=tariqt@nvidia.com \
--cc=ychemla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox