[dpdk-dev] [Bug 839] pdump: any subsequent runs of pdump_autotest fail
bugzilla at dpdk.org
bugzilla at dpdk.org
Tue Oct 26 14:09:10 CEST 2021
https://bugs.dpdk.org/show_bug.cgi?id=839
Bug ID: 839
Summary: pdump: any subsequent runs of pdump_autotest fail
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev at dpdk.org
Reporter: konstantin.ananyev at intel.com
Target Milestone: ---
rte_pdump_init() always allocates new memzone for pdump_stats.
Though rte_pdump_uninit() never frees it.
So the following combination will always fail:
rte_pdump_init(); rte_pdump_uninit(); rte_pdump_init();
The issue was caught by pdump_autotest UT.
While first test run successful, any consecutive runs
of this test-case will fail like that:
RTE>>pdump_autotest
IN PRIMARY PROCESS
rte_pdump_init(): cannot allocate pdump statistics
rte_pdump_init failed
...
I submitted fix to free pdum_stats memzone at rte_pdump_uninit():
https://patches.dpdk.org/project/dpdk/patch/20211026115301.5456-1-konstantin.ananyev@intel.com/
If you think it is not a proper way (instead we should keep memzone forever, or
so),
please feel free to supersede my patch with newer one.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the dev
mailing list