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 V2 3/4] net/mlx5e: Serialize TC and IPsec offload exclusion counters
Date: Wed, 30 Sep 2026 12:25:50 +0000	[thread overview]
Message-ID: <20260930122551.1EA3D1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930121119.141953-4-tariqt@nvidia.com>

> From: Cosmin Ratiu <cratiu@nvidia.com>
> 
> The counters enforcing TC and IPsec packet offload mutual exclusion are
> not consistently serialized. The IPsec add path conditionally takes the
> eswitch write lock, but neither release path takes it. The TC add path
> only holds the eswitch read lock, and devices without an eswitch cannot
> rely on that lock at all.
> 
> Concurrent read-modify-write operations on the same counter can lose an
> update. A stale nonzero count can keep rejecting offload requests after
> the last user has gone, while an undercount can allow conflicting
> offloads to coexist.
> 
> Move the counters into mdev->offload_block and protect all checks,
> increments and decrements with a dedicated mutex. Keep the
> opposing-counter check and reservation in the same critical section,
> independent of eswitch availability. Initialize the lock for the core
> device lifetime and add warnings for unbalanced releases.
> 
> Fixes: c8e350e62fc5 ("net/mlx5e: Make TC and IPsec offloads mutually exclusive on a netdev")
> Signed-off-by: Cosmin Ratiu <cratiu@nvidia.com>
> Reviewed-by: Dragos Tatulea <dtatulea@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/20260930121119.141953-1-tariqt@nvidia.com?part=3


  reply	other threads:[~2026-09-30 12:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 12:11 [PATCH net V2 0/4] net/mlx5e: Fix offload lifetime and exclusion bugs Tariq Toukan
2026-09-30 12:11 ` [PATCH net V2 1/4] net/mlx5e: ipsec: Block eswitch mode changes during policy creation Tariq Toukan
2026-09-30 12:25   ` sashiko-bot
2026-10-07  0:51   ` Jakub Kicinski
2026-09-30 12:11 ` [PATCH net V2 2/4] net/mlx5e: ipsec: Block eswitch mode changes before accessing priv->ipsec Tariq Toukan
2026-09-30 12:25   ` sashiko-bot
2026-10-07  0:51   ` Jakub Kicinski
2026-09-30 12:11 ` [PATCH net V2 3/4] net/mlx5e: Serialize TC and IPsec offload exclusion counters Tariq Toukan
2026-09-30 12:25   ` sashiko-bot [this message]
2026-09-30 12:11 ` [PATCH net V2 4/4] net/mlx5e: tc: Tie esw & accel blocking refs to the flow's lifetime Tariq Toukan
2026-09-30 12:25   ` sashiko-bot
2026-09-30 12:18 ` [PATCH net V2 0/4] net/mlx5e: Fix offload lifetime and exclusion bugs netdev-bot+sinfo

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=20260930122551.1EA3D1F00893@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