DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Marko Kovacevic <marko.kovacevic@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"xinfengx.zhao@intel.com" <xinfengx.zhao@intel.com>,
	"damianx.nowak@intel.com" <damianx.nowak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/3] examples/fips: fix hmac test failure
Date: Tue, 16 Apr 2019 14:49:31 +0000	[thread overview]
Message-ID: <VI1PR04MB4893FC50A158877CF50ADE8DE6240@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190416144931.CVL4tNjKsImLlI-52AdVXkC8swAK_JtyC7MpJ0pD0bU@z> (raw)

> Application was failing as the HMAC and
> Plain SHA fips request files are similar in a
> way that they both have SHA- in the top section to
> determine the hash algo and hash sizes. And HMAC having the
> algo in the second line but the Plain SHA in the third
> meant that when the HMAC files was used once it parsed the third
> line Plain SHA was set as the algo and not HMAC.
> 
> USER1: Failed to get capability for cdev 0
> USER1: Error -22: test block
> [L=20 SHAAlg=SHA_2]
> USER1: Error -22: Failed test /root/FIPS/HMAC/req/HMAC.req
> 
> Fixes: f4797bae0050 ("examples/fips_validation: support plain SHA")
> Cc: damianx.nowak@intel.com
> 
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
> ---

Series Applied to dpdk-next-crypto

Thanks.

             reply	other threads:[~2019-04-16 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 14:49 Akhil Goyal [this message]
2019-04-16 14:49 ` Akhil Goyal
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11 14:16 [dpdk-dev] [PATCH v1 " Marko Kovacevic
2019-04-15 15:04 ` [dpdk-dev] [PATCH v2 " Marko Kovacevic
2019-04-15 15:04   ` Marko Kovacevic

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=VI1PR04MB4893FC50A158877CF50ADE8DE6240@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=damianx.nowak@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=xinfengx.zhao@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).