>-----Original Message----- >From: De Lara Guarch, Pablo >Sent: Thursday, February 9, 2017 11:21 PM >To: De Lara Guarch, Pablo <[email protected]>; Mrozowicz, >SlawomirX <[email protected]>; Doherty, Declan ><[email protected]> >Cc: [email protected]; Mrozowicz, SlawomirX <[email protected]> >Subject: RE: [dpdk-dev] [PATCH v2] cryptodev: fix segmentation fault > > > >> -----Original Message----- >> From: dev [mailto:[email protected]] On Behalf Of De Lara Guarch, >> Pablo >> Sent: Thursday, February 09, 2017 3:29 PM >> To: Mrozowicz, SlawomirX; Doherty, Declan >> Cc: [email protected]; Mrozowicz, SlawomirX >> Subject: Re: [dpdk-dev] [PATCH v2] cryptodev: fix segmentation fault >> >> Hi Slawomir, >> >> > -----Original Message----- >> > From: dev [mailto:[email protected]] On Behalf Of Slawomir >> > Mrozowicz >> > Sent: Friday, February 03, 2017 3:55 PM >> > To: Doherty, Declan >> > Cc: [email protected]; Mrozowicz, SlawomirX >> > Subject: [dpdk-dev] [PATCH v2] cryptodev: fix segmentation fault >> > >> > This patch fix problem in function rte_cryptodev_devices_get(). >> > Program received signal SIGSEGV, Segmentation fault. >> > It rework the function to use correct types and clean up visibility. >> > It also fix Coverity ID 141073 >> > >> > Fixes: 38227c0e3ad2 ("cryptodev: retrieve device info") >> > >> > Signed-off-by: Slawomir Mrozowicz <[email protected]> >> >> I think this patch fixes coverity issue 141067, not 141073. >> Could you submit a v3 for this patch? Make sure to follow the format: > >I have done it for you. > >Applied to dpdk-next-crypto. >Thanks, > >Pablo
Thanks Pablo. Sławomir
