Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net] net/mlx5: Bridge, fix bogus MDB offload errors
Date: Wed, 21 Oct 2026 12:29:04 +0000	[thread overview]
Message-ID: <sashiko-outbox-180252@kernel.org> (raw)
In-Reply-To: <20261021122115.3737284-1-tariqt@nvidia.com>

> From: Gal Pressman <gal@nvidia.com>
> 
> MDB add operations are queued on the switchdev deferred queue
> (SWITCHDEV_F_DEFER), while vlan object deletions are handled
> synchronously.
> A 'bridge vlan del' can overtake an MDB add that is still queued, and
> the vlan is already gone by the time the driver is called.
> 
> The two operations are independent in practice: in my test, the MDB add
> is triggered by assigning the VF an IPv6 address (hence joining a
> solicited-node multicast group), while another process deletes the vlan
> from its representor.
> 
> Racing 'bridge mdb add' against concurrent 'bridge vlan del' could
> result in:
> [ ... ]
> 
> Fixes: 70f0302b3f20 ("net/mlx5: Bridge, implement mdb offload")
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> Reviewed-by: Cosmin Ratiu <cratiu@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261021122115.3737284-1-tariqt@nvidia.com?part=1


      reply	other threads:[~2026-10-21 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 12:21 [PATCH net] net/mlx5: Bridge, fix bogus MDB offload errors Tariq Toukan
2026-10-21 12:29 ` sashiko-bot [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=sashiko-outbox-180252@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox