From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 512] [dpdk-20.08]Crypto:fips_cryptodev test failed for TDES on aesni_mb, openssl and qat PMD
Date: Wed, 22 Jul 2020 01:48:50 +0000 [thread overview]
Message-ID: <bug-512-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=512
Bug ID: 512
Summary: [dpdk-20.08]Crypto:fips_cryptodev test failed for TDES
on aesni_mb, openssl and qat PMD
Product: DPDK
Version: 20.08
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
Created attachment 110
--> https://bugs.dpdk.org/attachment.cgi?id=110&action=edit
Detail info
DPDK version: 20.08.0-rc1 commit aae799d7dd4cc4d9c29cc665519cbec775b7bb6b
Other software versions:
nasm 2.14
intel-ipsec-mb 0.54
OpenSSL 1.1.1 11 Sep 2018
OS: Ub18.04.4 LTS (Bionic Beaver) 4.15.0-108-generic
Compiler: gcc version 7.5.0
Hardware platform: Purley Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz.
Test Setup:
Steps to reproduce:
1, Build DPDK and FIPS validation application
make -j 110 install T=x86_64-native-linuxapp-gcc MAKE_PAUSE=n
make -j 110 -C ./examples/fips_validation
2, Bind all qat vf device to vfio-pci driver
modprobe vfio
modprobe vfio-pci
lspci -D -d:37c8|awk '{print $1}'
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:1a:01.0 0000:1a:01.1
.....
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:1c:01.0 0000:1c:01.1
.....
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:1e:01.0 0000:1e:01.1
.....
3, Start fips_validation testing
./examples/fips_validation/build/fips_validation -l 9,10,66 -w 0000:1a:01.0
--socket-mem 2048,2048 --legacy-mem -n 6 -- --req-file /root/FIPS/TDES/req
--rsp-file /root/FIPS/TDES/resp --path-is-folder --cryptodev-id 0 --self-test
4, Compare fax/file & resp/file
diff /root/FIPS/TDES/resp/TCBCMonte3.rsp /root/FIPS/TDES/fax/TCBCMonte3.rsp |
grep -v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCMonte2.rsp /root/FIPS/TDES/fax/TCBCMonte2.rsp |
grep -v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCMMT2.rsp /root/FIPS/TDES/fax/TCBCMMT2.rsp | grep
-v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCMMT3.rsp /root/FIPS/TDES/fax/TCBCMMT3.rsp | grep
-v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCvartext.rsp /root/FIPS/TDES/fax/TCBCvartext.rsp |
grep -v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCpermop.rsp /root/FIPS/TDES/fax/TCBCpermop.rsp |
grep -v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCsubtab.rsp /root/FIPS/TDES/fax/TCBCsubtab.rsp |
grep -v '#' | grep -v '\---'
diff /root/FIPS/TDES/resp/TCBCvarkey.rsp /root/FIPS/TDES/fax/TCBCvarkey.rsp |
grep -v '#' | grep -v '\---'
Q1, Badcommit1: 32440cdf2 examples/fips_validation: fix parsing of TDES vectors
Failed files:
diff /root/FIPS/TDES/resp/TCBCvartext.rsp
/root/FIPS/TDES/fax/TCBCvartext.rsp | grep -v '#' | grep -v '\---' 466
failed --
diff
/root/FIPS/TDES/resp/TCBCpermop.rsp /root/FIPS/TDES/fax/TCBCpermop.rsp | grep
-v '#' | grep -v '\---' 231 failed
diff
/root/FIPS/TDES/resp/TCBCsubtab.rsp /root/FIPS/TDES/fax/TCBCsubtab.rsp | grep
-v '#' | grep -v '\---' 149 failed
diff
/root/FIPS/TDES/resp/TCBCvarkey.rsp /root/FIPS/TDES/fax/TCBCvarkey.rsp | grep
-v '#' | grep -v '\---' 408 failed
Failed point:
fax/TCBC*.rsp is missing a blank line & PLAINTEXT = 8000000000000000 in
"[DECRYPT] COUNT=0" part in below files.
Q1, Badcommit2: 2b84d2bd4 examples/fips_validation: fix count overwrite for
TDES
Failed files:
diff
/root/FIPS/TDES/resp/TCBCMonte3.rsp /root/FIPS/TDES/fax/TCBCMonte3.rsp | grep
-v '#' | grep -v '\---' failed
diff /root/FIPS/TDES/
fax/TCBCMonte2.rsp /root/FIPS/TDES/fax/TCBCMonte2.rsp | grep -v '#' | grep -v
'\---' failed
Failed point:
1,TDES/resp/TCBCMonte3.rsp add "COUNT = 0" and "COUNT = 1"(There are duplicated
"COUNT=1") in "[ENCRYPT]" & "[DECRYPT]" part.
2, TDES/resp/TCBCMonte2.rsp add
"COUNT = 0" and "COUNT = 1"(There are duplicated "COUNT=1") in file.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-07-22 1:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-512-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.