dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Junfeng Guo <junfengg@nvidia.com>
Cc: <vladimir.medvedkin@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH v2 2/2] net/ice: fix memory leak in raw pattern parse
Date: Tue, 7 Oct 2025 17:22:23 +0200	[thread overview]
Message-ID: <67090d9c-cb67-443c-81ea-899caed7022c@intel.com> (raw)
In-Reply-To: <200ebf9129483347f6263f130e167ff7fa42e7c3.1759840924.git.anatoly.burakov@intel.com>

On 10/7/2025 2:42 PM, Anatoly Burakov wrote:
> Currently, when parsing rte_flow raw type items, we allocate a bunch of
> internal structures, but if errors happen down the line we just quit and
> never free the memory we just allocated. Fix this by adding an error
> cleanup section.
> 
> Fixes: 25be39cc1760 ("net/ice: enable protocol agnostic flow offloading in FDIR")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> 

Fixline might be incorrect, i need to dig in a little more, as 
rte_malloc calls weren't there in that specific commit.

-- 
Thanks,
Anatoly

      reply	other threads:[~2025-10-07 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 11:37 [PATCH v1 1/1] net/ice: fix memory leak in raw pattern parse Anatoly Burakov
2025-10-07 12:42 ` [PATCH v2 1/2] net/ice: remove indirection for FDIR filters Anatoly Burakov
2025-10-07 12:42   ` [PATCH v2 2/2] net/ice: fix memory leak in raw pattern parse Anatoly Burakov
2025-10-07 15:22     ` Burakov, Anatoly [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=67090d9c-cb67-443c-81ea-899caed7022c@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=junfengg@nvidia.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=vladimir.medvedkin@intel.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).