From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id F402B4C9C for ; Wed, 13 Mar 2019 11:13:41 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Mar 2019 03:13:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,474,1544515200"; d="scan'208";a="141621866" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by orsmga002.jf.intel.com with ESMTP; 13 Mar 2019 03:13:40 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX107.ger.corp.intel.com (163.33.3.99) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 13 Mar 2019 10:13:38 +0000 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.230]) by irsmsx111.ger.corp.intel.com ([169.254.2.6]) with mapi id 14.03.0415.000; Wed, 13 Mar 2019 10:13:38 +0000 From: "Zhang, Roy Fan" To: "Pathak, Pravin" , "users@dpdk.org" Thread-Topic: DPDK 18.11 ASENI_MB segfault Thread-Index: AdTVNL7ki8Yim7N6Sz6UdI9Z93xBAgEUAYbQ Date: Wed, 13 Mar 2019 10:13:37 +0000 Message-ID: <9F7182E3F746AB4EA17801C148F3C604335A7ED7@IRSMSX101.ger.corp.intel.com> References: <168A68C163D584429EF02A476D5274424DEDC71C@FMSMSX108.amr.corp.intel.com> In-Reply-To: <168A68C163D584429EF02A476D5274424DEDC71C@FMSMSX108.amr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjAzYzc3OTgtZGNhNC00OGI4LTlhYjctZTNlMWM0NTlmYmZmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiUmE2NDVDU05yV3BDOWxTbkVoMFVibTIwZmJFRkthSHp1d29qMnhGSDB1SzVrMUNwbXp0TVd6dnY0YXFIaFZwMiJ9 dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] DPDK 18.11 ASENI_MB segfault X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 10:13:42 -0000 Hi, Can you share more information? Which process does the enqueue and dequeue operation? A segment of code or pseudo code would be nice. Regards, Fan > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Pathak, Pravin > Sent: Thursday, March 7, 2019 10:31 PM > To: users@dpdk.org > Subject: [dpdk-users] DPDK 18.11 ASENI_MB segfault >=20 > Hi - > I have multi-process application in which primary process initializes all= crypto > devices and sets up sessions. Secondary process uses the pre-initialized > devices and sessions. > It was working fine till DPDK 18.05. When switched to DPDK 18.11, second= ary > process started giving seg fault on receive. Primary process can still se= nd and > receive packets to/from crypto devices. > When switched to use HW crypto (QAT) instead of software crypto, same > application works fine on DPDK 18.11. Is the usage model correct? Anythi= ng > changed in DPDK 18.11 which might explain this? >=20 > Regards > Pravin >=20 > GDB backtrace >=20 > Program terminated with signal SIGSEGV, Segmentation fault. > #0 post_process_mb_job (qp=3D0x7007df2d600, job=3D0x55b48daa6b00) > at /.../dpdk-18.11/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c:931 > ---Type to continue, or q to quit--- > 931 if (likely(op->status =3D=3D > RTE_CRYPTO_OP_STATUS_NOT_PROCESSED)) { > [Current thread is 1 (Thread 0x7f7e8b2f4c00 (LWP 39715))] > (gdb) > (gdb) p op > $1 =3D (struct rte_crypto_op *) 0x0 > (gdb) p sess > $2 =3D > (gdb)