From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v1 0/7] IAVF Fixes
Date: Wed, 14 Oct 2026 16:18:43 +0100 [thread overview]
Message-ID: <cover.1791991100.git.anatoly.burakov@intel.com> (raw)
An assortment of IAVF flow-related memory leak fixes and cleanups.
Anatoly Burakov (7):
net/iavf: fix memory leak in flow teardown
net/iavf: fix null engine for egress security flows
net/iavf: fix generic flow error-path leaks
net/iavf: fix flow subscription metadata leaks
net/iavf: fix hash flow metadata leaks
net/iavf: fix IPsec flow metadata leaks
net/iavf: do not store ethdev pointer
drivers/net/intel/iavf/iavf.h | 9 +-
drivers/net/intel/iavf/iavf_ethdev.c | 13 +-
drivers/net/intel/iavf/iavf_fdir.c | 3 -
drivers/net/intel/iavf/iavf_fsub.c | 7 +-
drivers/net/intel/iavf/iavf_generic_flow.c | 58 +++----
drivers/net/intel/iavf/iavf_generic_flow.h | 4 +-
drivers/net/intel/iavf/iavf_hash.c | 24 ++-
drivers/net/intel/iavf/iavf_ipsec_crypto.c | 191 +++++++++++++++++----
drivers/net/intel/iavf/iavf_ipsec_crypto.h | 4 +-
drivers/net/intel/iavf/iavf_vchnl.c | 7 +-
10 files changed, 222 insertions(+), 98 deletions(-)
--
2.52.0
next reply other threads:[~2026-10-14 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 15:18 Anatoly Burakov [this message]
2026-10-14 15:18 ` [PATCH v1 1/7] net/iavf: fix memory leak in flow teardown Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 2/7] net/iavf: fix null engine for egress security flows Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 3/7] net/iavf: fix generic flow error-path leaks Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 4/7] net/iavf: fix flow subscription metadata leaks Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 5/7] net/iavf: fix hash flow " Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 6/7] net/iavf: fix IPsec " Anatoly Burakov
2026-10-14 15:18 ` [PATCH v1 7/7] net/iavf: do not store ethdev pointer Anatoly Burakov
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.1791991100.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@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