DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anurag Mandal <anurag.mandal@intel.com>
Cc: <dev@dpdk.org>, <anatoly.burakov@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH 4/8] net/ice: fix DCF QoS buffer leak on commit
Date: Fri, 6 Nov 2026 12:02:48 +0000	[thread overview]
Message-ID: <au3B6EplzDaouOsb@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <60f664e30d258546613eb746fb81f67e897a852c.1793871697.git.anurag.mandal@intel.com>

On Thu, Nov 05, 2026 at 09:47:21AM +0000, Anurag Mandal wrote:
> ice_dcf_hierarchy_commit() frees its temporary VF
> and TC bandwidth buffers only on the error path,
> so every successful commit still leaks them.
> 
> Free them on success as well.
> 
> Fixes: efd5d15a886b ("net/ice: fix memory leak in DCF QoS bandwidth config")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Anurag Mandal <anurag.mandal@intel.com>
> ---
>  drivers/net/intel/ice/ice_dcf_sched.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2026-11-06 12:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  9:47 [PATCH 0/8] net/ice: fix DCF memory leaks Anurag Mandal
2026-11-05  9:47 ` [PATCH 1/8] net/ice: fix DCF hardware init error path Anurag Mandal
2026-11-06 11:42   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 2/8] net/ice: fix DCF parent adapter " Anurag Mandal
2026-11-06 11:54   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 3/8] net/ice: fix DCF queue config buffer leak Anurag Mandal
2026-11-06 11:59   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 4/8] net/ice: fix DCF QoS buffer leak on commit Anurag Mandal
2026-11-06 12:02   ` Bruce Richardson [this message]
2026-11-05  9:47 ` [PATCH 5/8] net/ice: fix DCF QoS bandwidth replay config leak Anurag Mandal
2026-11-06 12:06   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 6/8] net/ice: fix DCF TM config leak on close Anurag Mandal
2026-11-06 12:09   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 7/8] net/ice: fix DCF representor info " Anurag Mandal
2026-11-06 12:15   ` Bruce Richardson
2026-11-05  9:47 ` [PATCH 8/8] net/ice: fix DCF port leak on probe failure Anurag Mandal
2026-11-06 12:18   ` Bruce Richardson
2026-11-07 23:52 ` [PATCH v2 0/8] net/ice: fix DCF memory leaks Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 1/8] net/ice: fix DCF hardware init error path Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 2/8] net/ice: fix DCF parent adapter " Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 3/8] net/ice: fix DCF queue config buffer leak Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 4/8] net/ice: fix DCF QoS buffer leak on commit Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 5/8] net/ice: fix DCF QoS bandwidth replay config leak Anurag Mandal
2026-11-09 17:40     ` Bruce Richardson
2026-11-07 23:52   ` [PATCH v2 6/8] net/ice: fix DCF TM config leak on close Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 7/8] net/ice: fix DCF representor info " Anurag Mandal
2026-11-07 23:52   ` [PATCH v2 8/8] net/ice: fix DCF port leak on probe failure Anurag Mandal
2026-11-09 17:50   ` [PATCH v2 0/8] net/ice: fix DCF memory leaks Bruce Richardson

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=au3B6EplzDaouOsb@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=anurag.mandal@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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