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 704ADA034F; Mon, 7 Feb 2022 01:36:00 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F07C54069D; Mon, 7 Feb 2022 01:35:59 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id A7E1A40685 for ; Mon, 7 Feb 2022 01:35:58 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 70F29A0352; Mon, 7 Feb 2022 01:35:58 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 934] crypto_aesni_mb PMD found crash in access mb_mgr on primary process after secondary process launch scan/probe Date: Mon, 07 Feb 2022 00:35:57 +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.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: changchun.zhang@oracle.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 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 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 https://bugs.dpdk.org/show_bug.cgi?id=3D934 Bug ID: 934 Summary: crypto_aesni_mb PMD found crash in access mb_mgr on primary process after secondary process launch scan/probe Product: DPDK Version: 20.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: cryptodev Assignee: dev@dpdk.org Reporter: changchun.zhang@oracle.com Target Milestone: --- This is a bug for AESNI_MB PMD in DPDK 20.11. The issue may have been resol= ved in latest DPDK, but wondering if a patch can be applied for 20.11. The AESNI_MB PMD in DPDK 20.11 does not work well in supporting multi-proce= ss. The crash can be seen by this sequence: 1. The crypto_aesni_mb is started successfuly on primary process by rte_vdev_init.=20 2. The secondary process launches the scanning/prob procedure and the prima= ry process received the sync req and replied the secondary process. The crypto_aesni_mb is also started by the probe on receiving the reply of the vdev_scan. 3. On primary process, the packet process tries to create the crypto session and it crashes on accessing the mb_mgr of dev->data->dev_private, in aesni_mb_set_session_auth_parameters() It is found in cryptodev_aesni_mb_create(),=20 mb_mgr =3D alloc_init_mb_mgr(vector_mode); can be triggered on both primary process and second process. Thus after the device is started on primary, the dev->data->dev_private->mb_mgr can be upd= ated when second process started the device again. This is incorrect.=20 The mb_mgr allocation should be limited to primary process. The same should= be applied to the qp->mb_mgr when setup the queue pair. --=20 You are receiving this mail because: You are the assignee for the bug.=