From: Mark Bloch <mbloch@nvidia.com>
To: Bernardo Soares <bsoares.it@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, saeedm@nvidia.com,
Vlad Buslov <vladbu@nvidia.com>
Subject: Re: [PATCH net v4 2/2] net/mlx5: Bridge, don't fail unlink of untracked/unsupported peer ports
Date: Tue, 22 Sep 2026 09:52:55 +0300 [thread overview]
Message-ID: <b9038692-e31b-4daf-8775-0bac3e99ceac@nvidia.com> (raw)
In-Reply-To: <20260918095931.29792-3-bsoares.it@gmail.com>
On 18/09/2026 12:59, Bernardo Soares wrote:
> mlx5_esw_bridge_vport_unlink() returns -EINVAL when the port isn't
> tracked by this instance's br_offloads. This is reachable on a sibling
> instance that registered its notifier after the port was already
> enslaved: it never saw the NETDEV_CHANGEUPPER link event, so
> peer_link() never created a peer port for it, but it does see the
> later unlink event and fails. Return 0 instead, and give
> mlx5_esw_bridge_vport_peer_unlink() the same merged_eswitch capability
> guard peer_link() already has, since without it peer_link() likewise
> never creates a port to unlink.
>
> This also matters beyond the -EINVAL itself:
> mlx5_esw_bridge_switchdev_port_event() runs on the per-netns
> netdev_chain, and notifier_from_errno(-EINVAL) sets NOTIFY_STOP_MASK,
> which call_netdevice_notifiers_info() checks to stop calling further
> listeners on that chain - so the old -EINVAL silently dropped the
> event for any listener registered later on the same chain, even
> though none of it was visible to user space since
> __netdev_upper_dev_unlink() discards the return value.
>
> Fixes: c358ea1741bc ("net/mlx5: Bridge, allow merged eswitch connectivity")
> Signed-off-by: Bernardo Soares <bsoares.it@gmail.com>
Thanks,
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Mark
> ---
> drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c b/drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c
> index ac90ccda1272..b4cf3c5ac0dd 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c
> @@ -1649,10 +1649,8 @@ int mlx5_esw_bridge_vport_unlink(struct net_device *br_netdev, u16 vport_num,
> int err;
>
> port = mlx5_esw_bridge_port_lookup(vport_num, esw_owner_vhca_id, br_offloads);
> - if (!port) {
> - NL_SET_ERR_MSG_MOD(extack, "Port is not attached to any bridge");
> - return -EINVAL;
> - }
> + if (!port)
> + return 0;
> if (port->bridge->ifindex != br_netdev->ifindex) {
> NL_SET_ERR_MSG_MOD(extack, "Port is attached to another bridge");
> return -EINVAL;
> @@ -1682,6 +1680,9 @@ int mlx5_esw_bridge_vport_peer_unlink(struct net_device *br_netdev, u16 vport_nu
> struct mlx5_esw_bridge_offloads *br_offloads,
> struct netlink_ext_ack *extack)
> {
> + if (!MLX5_CAP_ESW(br_offloads->esw->dev, merged_eswitch))
> + return 0;
> +
> return mlx5_esw_bridge_vport_unlink(br_netdev, vport_num, esw_owner_vhca_id, br_offloads,
> extack);
> }
next prev parent reply other threads:[~2026-09-22 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:59 [PATCH net v4 0/2] net/mlx5: Bridge, fix remaining switchdev ownership gaps on merged eswitch Bernardo Soares
2026-09-18 9:59 ` [PATCH net v4 1/2] net/mlx5: Bridge, don't fail switchdev events of sibling eswitch ports Bernardo Soares
2026-09-22 6:52 ` Mark Bloch
2026-09-18 9:59 ` [PATCH net v4 2/2] net/mlx5: Bridge, don't fail unlink of untracked/unsupported peer ports Bernardo Soares
2026-09-22 6:52 ` Mark Bloch [this message]
2026-09-22 6:42 ` [PATCH net v4 0/2] net/mlx5: Bridge, fix remaining switchdev ownership gaps on merged eswitch Mark Bloch
2026-09-23 1:20 ` patchwork-bot+netdevbpf
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=b9038692-e31b-4daf-8775-0bac3e99ceac@nvidia.com \
--to=mbloch@nvidia.com \
--cc=bsoares.it@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=vladbu@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