Skip to contentSkip to conversation

pdump: any subsequent runs of pdump_autotest fail

dpdk-dev [email protected] 1 participant 1 message Oct 26, 2021

lore
Share & tools
lore
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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/[email protected]/

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.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.