From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 669] Integrity check failure occurs when ciphering and integrity both enabled with snow3g algorithm
Date: Wed, 31 Mar 2021 05:28:38 +0000 [thread overview]
Message-ID: <bug-669-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=669
Bug ID: 669
Summary: Integrity check failure occurs when ciphering and
integrity both enabled with snow3g algorithm
Product: DPDK
Version: 20.02
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: tiger.liu@mavenir.com
Target Milestone: ---
Created attachment 153
--> https://bugs.dpdk.org/attachment.cgi?id=153&action=edit
information about the environment
Environment: 200Mbps traffic, 1 core, crypto_snow3g PMD without QAT for
ciphering and integrity
Detail:
1.Integrity check failure immediately occurs when sending 200Mbps traffic.
2.Not every packets are failing in the integrity check, the situation is like
this: packet NO.1 passed the check, NO.2-9 failed and 10-18 passed again, these
numbers are not stable every time.
3.The procedure of processing packets is firstly appending 4 bytes MACI by
integrity algorithm then ciphering the packets including the MACI.
4.Checking the error packets with dpdk-test-crypto-perf tool, the ciphered data
does not match with the original data.
5.Before pushing the data for ciphering by function
rte_cryptodev_enqueue_burst() to DPDK, the content is the same as the original
packets and the 4 bytes MACI is correct.
6.After getting the ciphered data by rte_cryptodev_dequeue_burst(),the ciphered
data is not correct, which probably means some error happens in DPDK code.
Additionally, Integrity check failure won’t occur when ciphering and integrity
both enabled with AES algorithm in the same environment.
We have got a response from Jayakumar Muthurajan, he said it is a missing
feature in the crypto-test when the size is different for encryption and
authentication. Please help check it.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-03-31 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 5:28 bugzilla [this message]
2024-03-15 9:04 ` [DPDK/cryptodev Bug " bugzilla
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-669-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 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).