[dpdk-dev] [PATCH 1/2] crypto/scheduler: set null pointer after freeing

Akhil Goyal akhil.goyal at nxp.com
Fri Apr 27 10:47:00 CEST 2018


Hi Pablo,

On 4/26/2018 8:39 PM, Pablo de Lara wrote:
> When freeing memory, pointers should be set to NULL,
> to avoid memory corruption/segmentation faults.

Shouldn't this be handled in the rte_free itself. A lot of other driver 
are also not setting null after rte_free.
This would require change at a lot of places if this is not handled in 
rte_free.

Thanks,
Akhil


More information about the dev mailing list