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 V3 1/3] net/mlx5: devcom, Base component size on linked devices
Date: Tue, 15 Sep 2026 11:47:54 +0000	[thread overview]
Message-ID: <20260915114754.CF2981F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915113459.3934760-2-tariqt@nvidia.com>

> From: Shay Drory <shayd@nvidia.com>
> 
> mlx5_devcom_comp_get_size() returns the component's kref count. That
> kref is bumped in mlx5_devcom_register_component() under comp_list_lock,
> before the comp_dev is linked onto comp_dev_list_head under comp->sem.
> The event broadcast (mlx5_devcom_locked_send_event()) walks that list.
> 
> Hence, a caller can read the expected size, but send_event won't be sent
> to all peers. In the SD group registration path, this lets a member
> broadcast its role-election event over an incomplete list, electing a
> primary that never completes the group, is never marked ready, and
> leaves the group with a stale primary.
> 
> Track the number of linked comp_devs in a dedicated counter, maintained
> under comp->sem together with the list add/remove, and return it from
> mlx5_devcom_comp_get_size().
> 
> Fixes: 9bb1ac80738a ("net/mlx5: devcom, Add component size getter")
> Signed-off-by: Shay Drory <shayd@nvidia.com>
> Reviewed-by: Akiva Goldberger <agoldberger@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Sashiko has reviewed this patch and found no issues. It looks great!

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


  reply	other threads:[~2026-09-15 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 11:34 [PATCH net V3 0/3] net/mlx5: SD LAG and devcom stability fixes Tariq Toukan
2026-09-15 11:34 ` [PATCH net V3 1/3] net/mlx5: devcom, Base component size on linked devices Tariq Toukan
2026-09-15 11:47   ` sashiko-bot [this message]
2026-09-15 11:34 ` [PATCH net V3 2/3] net/mlx5: SD, unload reps on shared FDB create error path Tariq Toukan
2026-09-15 11:47   ` sashiko-bot
2026-09-15 11:34 ` [PATCH net V3 3/3] net/mlx5: LAG, reload IB reps of LAG master before the rest Tariq Toukan
2026-09-15 11:47   ` sashiko-bot
2026-09-18  1:00 ` [PATCH net V3 0/3] net/mlx5: SD LAG and devcom stability fixes 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=20260915114754.CF2981F000FF@smtp.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