From: Bing Zhao <bingz@nvidia.com>
To: <dmitry.kozliuk@gmail.com>, <dev@dpdk.org>
Cc: <aman.deep.singh@intel.com>, <yuying.zhang@intel.com>,
<matan@nvidia.com>, <stable@dpdk.org>,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: [PATCH v2] app/testpmd: fix releasing action handle flush memory
Date: Mon, 25 Mar 2024 12:58:26 +0200 [thread overview]
Message-ID: <20240325105826.393231-1-bingz@nvidia.com> (raw)
In-Reply-To: <20240319093249.307606-1-bingz@nvidia.com>
The memory of the indirect action handles should be freed after
being destroyed in the flush. The behavior needs to be consistent
with the single handle destroy port_action_handle_destroy().
Or else, there would be some memory leak when closing / detaching a
port without quitting the application. In the meanwhile, since the
action handles are already destroyed, it makes no sense to hold the
indirect action software resources anymore.
Fixes: f7352c176bbf ("app/testpmd: fix use of indirect action after port close")
Cc: dmitry.kozliuk@gmail.com
Cc: stable@dpdk.org
Signed-off-by: Bing Zhao <bingz@nvidia.com>
Reviewed-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
v2: update the description
---
app/test-pmd/config.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
index ba1007ace6..f62ba90c87 100644
--- a/app/test-pmd/config.c
+++ b/app/test-pmd/config.c
@@ -1918,8 +1918,7 @@ port_action_handle_flush(portid_t port_id)
/* Poisoning to make sure PMDs update it in case of error. */
memset(&error, 0x44, sizeof(error));
if (pia->handle != NULL) {
- ret = pia->type ==
- RTE_FLOW_ACTION_TYPE_INDIRECT_LIST ?
+ ret = pia->type == RTE_FLOW_ACTION_TYPE_INDIRECT_LIST ?
rte_flow_action_list_handle_destroy
(port_id, pia->list_handle, &error) :
rte_flow_action_handle_destroy
@@ -1929,11 +1928,9 @@ port_action_handle_flush(portid_t port_id)
pia->id);
ret = port_flow_complain(&error);
}
- tmp = &pia->next;
- } else {
- *tmp = pia->next;
- free(pia);
}
+ *tmp = pia->next;
+ free(pia);
}
return ret;
}
--
2.34.1
next prev parent reply other threads:[~2024-03-25 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:32 [PATCH] " Bing Zhao
2024-03-19 14:20 ` Ferruh Yigit
2024-03-25 9:03 ` Bing Zhao
2024-03-25 10:58 ` Bing Zhao [this message]
2024-04-18 21:41 ` [PATCH v2] " Ferruh Yigit
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=20240325105826.393231-1-bingz@nvidia.com \
--to=bingz@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--cc=yuying.zhang@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).