From: Anurag Mandal <anurag.mandal@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, anatoly.burakov@intel.com,
Anurag Mandal <anurag.mandal@intel.com>
Subject: [PATCH 0/8] net/ice: fix DCF memory leaks
Date: Thu, 5 Nov 2026 09:47:17 +0000 [thread overview]
Message-ID: <cover.1793871697.git.anurag.mandal@intel.com> (raw)
This patch series fixes memory leaks, and related error path issues,
in the ice DCF driver.
1. The VF VSI map leaked on DCF hardware init failure, and a failed
VLAN capability query left the interrupt callback registered.
2. A failed DCF parent adapter init leaked the dummy main VSI, and a
failed flow init also leaked the DDP parser and flow engine state.
3. The queue config message leaked when the required RXDID was not
supported.
4. The temporary QoS bandwidth buffers still leaked on every
successful hierarchy commit.
5. The QoS bandwidth config saved for replay leaked on every commit,
close and reset.
6. TM nodes and shaper profiles leaked on close when the hierarchy was
never committed.
7. The representor info leaked when the DCF port was closed.
8. A failed probe left the DCF port and its representors behind. A
representor type other than VF is now rejected before the DCF port
is created.
Anurag Mandal (8):
net/ice: fix DCF hardware init error path
net/ice: fix DCF parent adapter init error path
net/ice: fix DCF queue config buffer leak
net/ice: fix DCF QoS buffer leak on commit
net/ice: fix DCF QoS bandwidth replay config leak
net/ice: fix DCF TM config leak on close
net/ice: fix DCF representor info leak on close
net/ice: fix DCF port leak on probe failure
drivers/net/intel/ice/ice_dcf.c | 27 ++++++++++++---
drivers/net/intel/ice/ice_dcf_ethdev.c | 48 +++++++++++++++++++-------
drivers/net/intel/ice/ice_dcf_parent.c | 9 +++--
drivers/net/intel/ice/ice_dcf_sched.c | 4 +++
4 files changed, 68 insertions(+), 20 deletions(-)
--
2.25.1
next reply other threads:[~2026-11-05 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 9:47 Anurag Mandal [this message]
2026-11-05 9:47 ` [PATCH 1/8] net/ice: fix DCF hardware init error path Anurag Mandal
2026-11-05 9:47 ` [PATCH 2/8] net/ice: fix DCF parent adapter " Anurag Mandal
2026-11-05 9:47 ` [PATCH 3/8] net/ice: fix DCF queue config buffer leak Anurag Mandal
2026-11-05 9:47 ` [PATCH 4/8] net/ice: fix DCF QoS buffer leak on commit Anurag Mandal
2026-11-05 9:47 ` [PATCH 5/8] net/ice: fix DCF QoS bandwidth replay config leak Anurag Mandal
2026-11-05 9:47 ` [PATCH 6/8] net/ice: fix DCF TM config leak on close Anurag Mandal
2026-11-05 9:47 ` [PATCH 7/8] net/ice: fix DCF representor info " Anurag Mandal
2026-11-05 9:47 ` [PATCH 8/8] net/ice: fix DCF port leak on probe failure Anurag Mandal
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=cover.1793871697.git.anurag.mandal@intel.com \
--to=anurag.mandal@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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