From: Anoob Joseph <anoobj@marvell.com>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] test/crypto: fix missing operation status check
Date: Fri, 10 Jan 2020 10:54:28 +0000 [thread overview]
Message-ID: <MN2PR18MB2877209BC0E11D9EB81BA0FADF380@MN2PR18MB2877.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20191220125852.3551-2-adamx.dybkowski@intel.com>
>
> This patch adds checking of the symmetric crypto operation status that was
> silently skipped before. It fixes the wireless algorithms session creation
> (SNOW3G, KASUMI, ZUC) and passing of the digest data for the verification by
> PMD. Also fixed the missing aad padding issue revealed after op status checking
> was introduced.
>
> Fixes: c0f87eb5252b ("cryptodev: change burst API to be crypto op oriented")
> Fixes: 77a217a19bb7 ("test/crypto: add AES-CCM tests")
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
> app/test/test_cryptodev.c | 96 +++++++++++++++++++++------------------
> 1 file changed, 52 insertions(+), 44 deletions(-)
>
Tested-by: Ankur Dwivedi <adwivedi@marvell.com>
Reviewed-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2020-01-10 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 11:50 [dpdk-dev] [PATCH] test/crypto: add operation status checks Adam Dybkowski
2019-12-20 12:38 ` Trahe, Fiona
2019-12-20 12:46 ` Dybkowski, AdamX
2019-12-20 12:58 ` [dpdk-dev] [PATCH v2 0/1] test/crypto: fix missing operation status check Adam Dybkowski
2019-12-20 12:58 ` [dpdk-dev] [PATCH v2 1/1] " Adam Dybkowski
2019-12-20 13:06 ` Trahe, Fiona
2020-01-10 10:54 ` Anoob Joseph [this message]
2020-01-15 15:54 ` Akhil Goyal
2020-01-17 16:21 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
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=MN2PR18MB2877209BC0E11D9EB81BA0FADF380@MN2PR18MB2877.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).