From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: dev@dpdk.org, "Kusztal,
ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
"Cel, TomaszX" <tomaszx.cel@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] common/qat: fix for invalid response from firmware
Date: Sat, 27 Oct 2018 02:15:26 +0200 [thread overview]
Message-ID: <4865602.c1DW6WG4oq@xps> (raw)
In-Reply-To: <06EE24DD0B19E248B53F6DC8657831559EB482@HASMSX110.ger.corp.intel.com>
24/10/2018 17:11, Kusztal, ArkadiuszX:
> From: Trahe, Fiona
> >
> > Check that the firmware response has a bit set indicating it's valid before
> > dereferencing the rest of the response contents.
> >
> > Fixes: 0bdd36e12245 ("crypto/qat: make dequeue function generic")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
>
> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-10-27 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 23:39 Fiona Trahe
2018-10-24 15:11 ` Kusztal, ArkadiuszX
2018-10-27 0:15 ` Thomas Monjalon [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=4865602.c1DW6WG4oq@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=stable@dpdk.org \
--cc=tomaszx.cel@intel.com \
--cc=tomaszx.jozwiak@intel.com \
/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).