patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "Yu, PingX" <pingx.yu@intel.com>
Cc: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Daly, Lee" <lee.daly@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"O'Hare, Cathal" <cathal.ohare@intel.com>
Subject: Re: [dpdk-stable] [PATCH 17.11] cryptodev: fix missing device id range checking
Date: Thu, 27 Feb 2020 08:48:20 +0000	[thread overview]
Message-ID: <4ce83fc95b0beaa1e1ca283b3b4f22aa254d911d.camel@debian.org> (raw)
In-Reply-To: <86d6bc45c120400f88584451f3eefb98@intel.com>

Great, thank you very much for confirming!

On Thu, 2020-02-27 at 01:48 +0000, Yu, PingX wrote:
> 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@debian.org
> > ]
> > Sent: Wednesday, February 26, 2020 5:53 PM
> > To: Yu, PingX <
> > pingx.yu@intel.com
> > >
> > Cc: Dybkowski, AdamX <
> > adamx.dybkowski@intel.com
> > >; 
> > stable@dpdk.org
> > ;
> > Trahe, Fiona <
> > fiona.trahe@intel.com
> > >; Mcnamara, John
> > <
> > john.mcnamara@intel.com
> > >; Daly, Lee <
> > lee.daly@intel.com
> > >; Xu, Qian Q
> > <
> > qian.q.xu@intel.com
> > >; Yigit, Ferruh <
> > ferruh.yigit@intel.com
> > >; O'Hare, Cathal
> > <
> > cathal.ohare@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@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
-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2020-02-27  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 15:40 Adam Dybkowski
2020-02-21 16:12 ` Luca Boccassi
2020-02-26  9:52   ` Luca Boccassi
2020-02-27  1:48     ` Yu, PingX
2020-02-27  8:48       ` Luca Boccassi [this message]
2020-02-21 16:16 ` Trahe, Fiona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ce83fc95b0beaa1e1ca283b3b4f22aa254d911d.camel@debian.org \
    --to=bluca@debian.org \
    --cc=adamx.dybkowski@intel.com \
    --cc=cathal.ohare@intel.com \
    --cc=ferruh.yigit@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=lee.daly@intel.com \
    --cc=pingx.yu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).