Re: [dpdk-dev] [PATCH v4] crypto/qat: add null point check and fix mem leak

2018-01-31 Thread Thomas Monjalon
> > There are several func calls to rte_zmalloc() which don't do null > > point check on the return value. And before return, the memory is not > > freed. Fix it by adding null point check and rte_free(). > > > > Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices") > > Fixes: e09231eaa2

Re: [dpdk-dev] [PATCH v4] crypto/qat: add null point check and fix mem leak

2018-01-25 Thread Trahe, Fiona
> -Original Message- > From: Yong Wang [mailto:wang.yon...@zte.com.cn] > Sent: Thursday, January 25, 2018 6:53 AM > To: Trahe, Fiona > Cc: dev@dpdk.org; Yong Wang > Subject: [PATCH v4] crypto/qat: add null point check and fix mem leak > > There are several func calls to rte_zmalloc() w

[dpdk-dev] [PATCH v4] crypto/qat: add null point check and fix mem leak

2018-01-24 Thread Yong Wang
There are several func calls to rte_zmalloc() which don't do null point check on the return value. And before return, the memory is not freed. Fix it by adding null point check and rte_free(). Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices") Fixes: e09231eaa2af ("crypto/qat: add SGL