Hi,
On 11/03/2026 9:53 AM, Dariusz Sosnowski wrote:
Whenever a new set of representors are probed by mlx5 driver
on Multiport E-Switch setup using these device arguments:
0000:08:00.0,dv_flow_en=2,representor=(pf1)vf1
mlx5 driver should create 2 DPDK ports.
One for 1st physical port (transfer proxy) and another for
PF1VF1 representor. Parentheses are used in representor argument
to indicate that physical port related to PF1VF1 should be ignored.
Offending patch has introduced a regression to ignore logic.
Whenever mlx5 driver checked if related physical port should be probed
and if representor_match_uplink() returned false (as it should),
this result was ignored and probing continued.
If requested VF/SF index matched PF index, physical port was probed.
This patch fixes that by adding explicit rejection of spawning physical
ports for VF/SF representors if checked port is a physical port and
driver have not already spawned it.
Fixes: f363bbe2c036 ("net/mlx5: fix probing to allow BlueField Socket Direct")
Signed-off-by: Dariusz Sosnowski <[email protected]>
Acked-by: Bing Zhao <[email protected]>
Patch squashed into relevant commit in next-net-mlx,
Kindest regards
Raslan Darawsheh
