DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Maayan Kashani <mkashani@nvidia.com>, dev@dpdk.org
Cc: stable@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Michael Baum <michaelba@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix panic for non template age rules flush
Date: Mon, 18 Aug 2025 09:36:36 +0300	[thread overview]
Message-ID: <c13ff67b-a887-40a3-a245-9004396d56df@nvidia.com> (raw)
In-Reply-To: <20250810064732.74932-1-mkashani@nvidia.com>

Hi,


On 10/08/2025 9:47 AM, Maayan Kashani wrote:
> When a user creates a non-template rule with both age and counter actions,
> both actions share the same counter.
> If a flow flush occurs, the rule is destroyed and the counter is released.
> However, the age sampling callback may still access the age/counter during
> the free, leading to a panic on assertion in debug mode.
> 
> This creates a race condition: one thread samples the age while another
> releases the age/counter info used by the age action.
> The fix is to ignore this case where the age is
> free and counter not freed yet,
> or the counter was freed during the age check.
> 
> Fixes: 04a4de756e14 ("net/mlx5: support flow age action with HWS")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


  reply	other threads:[~2025-08-18  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10  6:47 Maayan Kashani
2025-08-18  6:36 ` Raslan Darawsheh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-09 10:25 Maayan Kashani

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=c13ff67b-a887-40a3-a245-9004396d56df@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@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;
as well as URLs for NNTP newsgroup(s).