> -----Original Message----- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of De Lara Guarch, > Pablo > Sent: Friday, February 10, 2017 11:26 AM > To: Mrozowicz, SlawomirX; Doherty, Declan > Cc: dev@dpdk.org; Mrozowicz, SlawomirX > Subject: Re: [dpdk-dev] [PATCH v2] app/test-crypto-perf: fix segmentation > fault when use qat pmd > > Hi Slawomir, > > > -----Original Message----- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Slawomir > > Mrozowicz > > Sent: Thursday, February 09, 2017 1:57 PM > > To: Doherty, Declan > > Cc: dev@dpdk.org; Mrozowicz, SlawomirX > > Subject: [dpdk-dev] [PATCH v2] app/test-crypto-perf: fix segmentation > fault > > when use qat pmd > > > > Fix segmentation fault happened when use QAT PMD's kasumi, snow3g or > > zug > > algorithm to do cipher-then-auth performance test application. > > The mentioned algorithms required authentication key data be set. > > This patch fix issue that gmac algorithm required authentication key data > > be set value equal to cipher key data. > > > > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test > > application") > > > > Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozow...@intel.com> > > This also happened for other SW PMDs and not just QAT, but an incorrect > implementation in them was hiding this issue. > I will reword this commit. Also, make sure to run check-git-log.sh next time, > as I am seeing: > > Wrong headline lowercase: > app/test-crypto-perf: fix segmentation fault when use qat pmd > Headline too long: > app/test-crypto-perf: fix segmentation fault when use qat pmd > > Apart from this, > > Acked-by: Pablo de Lara <pablo.de.lara.gua...@intel.com> >
Applied to dpdk-next-crypto. Thanks, Pablo
