From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 33DC4A034F; Wed, 31 Mar 2021 07:28:41 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BE2B24069E; Wed, 31 Mar 2021 07:28:40 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 9BA0740141 for ; Wed, 31 Mar 2021 07:28:39 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 6607CA0547; Wed, 31 Mar 2021 07:28:39 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Wed, 31 Mar 2021 05:28:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: cryptodev X-Bugzilla-Version: 20.02 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tiger.liu@mavenir.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 669] Integrity check failure occurs when ciphering and integrity both enabled with snow3g algorithm X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D669 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=3D153&action=3Dedit information about the environment Environment: 200Mbps traffic, 1 core, crypto_snow3g PMD without QAT for ciphering and integrity Detail:=20 1.Integrity check failure immediately occurs when sending 200Mbps traffic. 2.Not every packets are failing in the integrity check, the situation is li= ke this: packet NO.1 passed the check, NO.2-9 failed and 10-18 passed again, t= hese 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 origi= nal packets and the 4 bytes MACI is correct. 6.After getting the ciphered data by rte_cryptodev_dequeue_burst(),the ciph= ered data is not correct, which probably means some error happens in DPDK code. Additionally, Integrity check failure won=E2=80=99t occur when ciphering an= d integrity both enabled with AES algorithm in the same environment.=20 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. --=20 You are receiving this mail because: You are the assignee for the bug.=