patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix null auth issues when using vfio_pci
Date: Mon, 21 Oct 2019 10:56:07 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435A2179F2B@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB6639CD6642AEC0CF7A04F28EE6690@VE1PR04MB6639.eurprd04.prod.outlook.com>

Thanks for applying Akhil.
We'd just spotted the incorrect fixline, and were going to send a v2, but I see you fixed on the fly. Thanks.
Just including here for the stable patch - the correct fixline is:

Fixes: 4e0955bddb08 ("crypto/qat: fix null auth algo overwrite")

> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Monday, October 21, 2019 10:45 AM
> To: Trahe, Fiona <fiona.trahe@intel.com>; dev@dpdk.org
> Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; stable@dpdk.org
> Subject: RE: [PATCH] crypto/qat: fix null auth issues when using vfio_pci
> 
> 
> >
> >
> > > >
> > > > When running auth NULL cases while using
> > > > vfio_pci, DMAR read/write faults appear. It
> > > > happens even if digest_length is set to 0.
> > > > This is caused by auth_res_addr initialized
> > > > as 0x0.
> > > >
> > > > Fixes: 4e0955bddb08
> > > > Cc: Fiona Trahe <fiona.trahe@intel.com>
> > > >
> > > > Signed-off-by: Damian Nowak <damianx.nowak@intel.com>
> > > Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> >
> > Applied to dpdk-next-crypto
> >
> > Thanks
> 
> Cc: stable@dpdk.org

      reply	other threads:[~2019-10-21 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190809092901.17788-1-damianx.nowak@intel.com>
     [not found] ` <348A99DA5F5B7549AA880327E580B435A2176158@IRSMSX101.ger.corp.intel.com>
     [not found]   ` <VE1PR04MB6639361CA412A5E825E84D44E6690@VE1PR04MB6639.eurprd04.prod.outlook.com>
2019-10-21  9:44     ` Akhil Goyal
2019-10-21 10:56       ` Trahe, Fiona [this message]

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=348A99DA5F5B7549AA880327E580B435A2179F2B@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=akhil.goyal@nxp.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).