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/mlx5e: Fix false WARN_ON_ONCE in flow steering cleanup during RX init failure
Date: Mon, 26 Oct 2026 08:57:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-184712@kernel.org> (raw)
In-Reply-To: <20261026072253.4118892-1-tariqt@nvidia.com>

> From: Alexei Lazar <alazar@nvidia.com>
> 
> In mlx5e_init_nic_rx(), a failure subsequent to
> mlx5e_create_flow_steering() initiates an error cleanup flow, where
> mlx5e_destroy_flow_steering() calls mlx5e_del_vlan_rules() that contains
> WARN_ON_ONCE(fs->state_destroy).
> This warning fires because state_destroy is set before flow steering is
> fully initialized.
> 
> To fix this, initialize NIC flow steering with state_destroy cleared,
> and set state_destroy only after profile->init_rx() succeeds.
> This keeps the flag cleared while mlx5e_create_flow_steering() is
> building its tables, so its internal error paths can destroy partially
> created flow steering without triggering the warning.
> 
> [ ... ]
> Fixes: 8c7353b6f716 ("net/mlx5e: Fix VLAN cleanup flow")
> Signed-off-by: Alexei Lazar <alazar@nvidia.com>
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> Reviewed-by: Shahar Shitrit <shshitrit@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/20261026072253.4118892-1-tariqt@nvidia.com?part=1


  parent reply	other threads:[~2026-10-26  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  7:22 [PATCH net] net/mlx5e: Fix false WARN_ON_ONCE in flow steering cleanup during RX init failure Tariq Toukan
2026-10-26  7:26 ` netdev-bot+sinfo
2026-10-26  8:57 ` sashiko-bot [this message]
2026-10-28 22:39 ` Jakub Kicinski

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-184712@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