From: Akhil Goyal <gakhil@marvell.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix illegal access of an array
Date: Tue, 27 Jul 2021 17:36:04 +0000 [thread overview]
Message-ID: <PH0PR18MB449141FF568BCB8C7787E4B7D8E99@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB2575D65EA4C930FEDE07D768EDE99@SN6PR11MB2575.namprd11.prod.outlook.com>
> > Fix possible access of an array by negative index in function
> > qat_sym_qp_setup.
> >
> > Fixes: 8f393c4ffdc1 ("common/qat: support GEN4 devices") Coverity issue:
> > 372131 Coverity issue: 372134
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>
> Acked-by: Adam Dybkowski <adamx.dybkowski@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2021-07-27 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:47 Arek Kusztal
2021-07-27 9:31 ` Dybkowski, AdamX
2021-07-27 17:36 ` Akhil Goyal [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=PH0PR18MB449141FF568BCB8C7787E4B7D8E99@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adamx.dybkowski@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@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).