[dpdk-stable] [PATCH 17.11] cryptodev: fix missing device id range checking

[Yu, PingX]

Luca, 
The issue is fixed with patch https://mails.dpdk.org/archives/stable/2020-February/020657.html.
You can go ahead now.

Regards,
Yu Ping


> -----Original Message-----
> From: Luca Boccassi [mailto:bluca at debian.org]
> Sent: Wednesday, February 26, 2020 5:53 PM
> To: Yu, PingX <pingx.yu at intel.com>
> Cc: Dybkowski, AdamX <adamx.dybkowski at intel.com>; stable at dpdk.org;
> Trahe, Fiona <fiona.trahe at intel.com>; Mcnamara, John
> <john.mcnamara at intel.com>; Daly, Lee <lee.daly at intel.com>; Xu, Qian Q
> <qian.q.xu at intel.com>; Yigit, Ferruh <ferruh.yigit at intel.com>; O'Hare, Cathal
> <cathal.ohare at intel.com>
> Subject: Re: [dpdk-stable] [PATCH 17.11] cryptodev: fix missing device id range
> checking
> 
> On Fri, 2020-02-21 at 16:12 +0000, Luca Boccassi wrote:
> > On Fri, 2020-02-21 at 16:40 +0100, Adam Dybkowski wrote:
> > > This patch adds range-checking of the device id passed from the user
> > > app code. It prevents out-of-range array accesses which in some
> > > situations resulted in an application crash (segfault).
> > >
> > > Fixes: 72de277dd423 ("cryptodev: fix checks related to device id")
> > >
> > > Signed-off-by: Adam Dybkowski <
> > > adamx.dybkowski at intel.com
> > > >
> >
> > Thanks, applied and pushed.
> >
> > Yu, would you have time to re-test the head of the 17.11 branch to see
> > if this fixes the issue with QAT?
> >
> > Thanks!
> 
> Hello Yu,
> 
> Any update on this? We are just waiting on re-validating the crypto devices (no
> need for a full run) for the release.
> 
> Thank you!
> 
> --
> Kind regards,
> Luca Boccassi