From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
"Zhang, Ke1X" <ke1x.zhang@intel.com>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3] app/testpmd: fix issue with memory leaks when quit testpmd
Date: Wed, 8 Jun 2022 13:06:06 +0100 [thread overview]
Message-ID: <a498809b-c696-24e1-cb26-13fc09fef88c@xilinx.com> (raw)
In-Reply-To: <DM6PR11MB3516E9C31B7CE51B18C871618EE59@DM6PR11MB3516.namprd11.prod.outlook.com>
On 4/4/2022 4:34 PM, Zhang, Yuying wrote:
> Hi Ke,
>
>> -----Original Message-----
>> From: Zhang, Ke1X <ke1x.zhang@intel.com>
>> Sent: Friday, March 25, 2022 4:36 PM
>> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Singh, Aman Deep
>> <aman.deep.singh@intel.com>; Zhang, Yuying <yuying.zhang@intel.com>;
>> dev@dpdk.org
>> Cc: Zhang, Ke1X <ke1x.zhang@intel.com>
>> Subject: [PATCH v3] app/testpmd: fix issue with memory leaks when quit
>> testpmd
>>
>> A multicast address pool is allocated for a port when using mcast_addr
>> testpmd commands.
>>
>> When closing a port or stopping testpmd, this pool was not freed, resulting in
>> a leak.This issue has been caught using ASan.
>>
>> Free this pool when closing the port.
>>
>> Error info as following:
>> ERROR: LeakSanitizer: detected memory leaksDirect leak of
>> 192 byte(s)
>> 0 0x7f6a2e0aeffe in __interceptor_realloc
>> (/lib/x86_64-linux-gnu/libasan.so.5+0x10dffe)
>> 1 0x565361eb340f in mcast_addr_pool_extend
>> ../app/test-pmd/config.c:5162
>> 2 0x565361eb3556 in mcast_addr_pool_append
>> ../app/test-pmd/config.c:5180
>> 3 0x565361eb3aae in mcast_addr_add
>> ../app/test-pmd/config.c:5243
>>
>> Signed-off-by: Ke Zhang <ke1x.zhang@intel.com>
>
> Acked-by: Yuying Zhang <yuying.zhang@intel.com>
>
Fixes: 8fff667578a7 ("app/testpmd: new command to add/remove
multicast MAC addresses")
Cc: stable@dpdk.org
Acked-by: Ferruh Yigit <ferruh.yigit@xilinx.com>
Applied to dpdk-next-net/main, thanks.
<...>
>> pmd/testpmd.c b/app/test-pmd/testpmd.c index fe2ce19f99..1861a02c2f
>> 100644
>> --- a/app/test-pmd/testpmd.c
>> +++ b/app/test-pmd/testpmd.c
>> @@ -3137,6 +3137,7 @@ close_port(portid_t pid)
>> }
>>
>> if (is_proc_primary()) {
>> + mcast_addr_pool_destroy(pi);
>> port_flow_flush(pi);
>> port_flex_item_flush(pi);
>> rte_eth_dev_close(pi);
'rte_eth_dev_close()' may fail, like if the port is not stopped, in that
case mcast pool will be freed although port is not closed.
This can be prevented by saving existing mcast poll and restore it if
close failed, but I think it doesn't worth the complexity it brings, so
OK to continue as it is.
next prev parent reply other threads:[~2022-06-08 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 2:06 [PATCH] " Ke Zhang
2022-03-04 16:43 ` Ferruh Yigit
2022-03-08 6:05 ` Zhang, Ke1X
2022-03-14 5:52 ` [PATCH v2] " Ke Zhang
2022-03-14 9:10 ` David Marchand
2022-03-15 10:06 ` Zhang, Yuying
2022-03-25 8:35 ` [PATCH v3] " Ke Zhang
2022-04-04 15:34 ` Zhang, Yuying
2022-06-08 12:06 ` Ferruh Yigit [this message]
2022-03-25 8:30 Ke Zhang
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=a498809b-c696-24e1-cb26-13fc09fef88c@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ke1x.zhang@intel.com \
--cc=xiaoyun.li@intel.com \
--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).