[dpdk-dev] [PATCH v2] test: Fix memory corruption issues which fails the link_bonding test.

Ferruh Yigit ferruh.yigit at intel.com
Mon Jul 31 17:25:14 CEST 2017


On 7/12/2017 11:23 AM, Declan Doherty wrote:
> On 10/07/17 12:13, Herbert Guan wrote:
>> Patch V2: fix build warnings by deleting unused variables.
>>
>> There were double-free problems in some test cases, which will cause
>> a duplicated mbuf will be added into mempool.  After double-free,
>> some new allocated mbuf will hold a same address and thus cause the
>> memory corruption.
>>
>> Another minor issue is that in some test cases, allocated mbuf will
>> not be released after test case exits.  Hopefully these leaked mbuf
>> will be released by the next test case in its setup phase when
>> stopping the virtual pmd ports, while this do is a memory leak of
>> the exited test case.
>>
>> To fix above 2 issues, this patch will do:
>> 1) Release virtual pmd ports' tx queue in the clean up function
>>     remove_slaves_and_stop_bonded_device() of each test cases.
>> 2) Do not release allocated mbufs for test bursts.  These mbufs
>>     will be released in remove_slaves_and_stop_bonded_device() when
>>     test case exits.
>>
>> Signed-off-by: Herbert Guan <herbert.guan at arm.com>
>> ---
> ...
>>
> 
> Acked-by: Declan Doherty <declan.doherty at intel.com>

Applied to dpdk-next-net/master, thanks.


More information about the dev mailing list