On Mon, Feb 09, 2026 at 04:14:40PM +0000, Max Tottenham wrote:
> When creating vport actions for hotplugged SF/VF representors in
> flow_hw_create_vport_action(), the function incorrectly used
> is_unified_fdb(priv) where priv is the representor's private data.
>
> However, the vport action is stored in proxy_priv->hw_vport[] and
> will be used by flows on the proxy port. Since representors have
> unified_fdb_en=false while the proxy port (PF) may have it enabled,
> this caused a flag mismatch:
>
> - Proxy port (port 0): unified FDB enabled
> - SF representors (ports 2, 3): unified FDB disabled
> - Vport actions for SFs created with MLX5DR_ACTION_FLAG_HWS_FDB
> - But flows on proxy port use unified FDB mode
>
> This resulted in REPRESENTED_PORT actions counting packets correctly
> (flow matches work) but not actually forwarding them to the
> destination vport.
>
> Fix by using is_unified_fdb(proxy_priv) to ensure the vport action
> flags match the proxy port's FDB mode, which is where the action
> will actually be used.
>
> Fixes: flow_hw_create_vport_action() vport flag selection
Please use the following for Fixes tag:
Fixes: ac687bb002c9 ("net/mlx5: support unified FDB domain")
> Signed-off-by: Max Tottenham <[email protected]>
