From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 240837D52 for ; Thu, 7 Mar 2019 23:30:37 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2019 14:30:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,453,1544515200"; d="scan'208,217";a="326445371" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 07 Mar 2019 14:30:37 -0800 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 7 Mar 2019 14:30:36 -0800 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.86]) by fmsmsx116.amr.corp.intel.com ([169.254.2.2]) with mapi id 14.03.0415.000; Thu, 7 Mar 2019 14:30:36 -0800 From: "Pathak, Pravin" To: "users@dpdk.org" Thread-Topic: DPDK 18.11 ASENI_MB segfault Thread-Index: AdTVNL7ki8Yim7N6Sz6UdI9Z93xBAg== Date: Thu, 7 Mar 2019 22:30:36 +0000 Message-ID: <168A68C163D584429EF02A476D5274424DEDC71C@FMSMSX108.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjAzYzc3OTgtZGNhNC00OGI4LTlhYjctZTNlMWM0NTlmYmZmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiUmE2NDVDU05yV3BDOWxTbkVoMFVibTIwZmJFRkthSHp1d29qMnhGSDB1SzVrMUNwbXp0TVd6dnY0YXFIaFZwMiJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.1.200.108] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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: Thu, 07 Mar 2019 22:30:38 -0000 Hi - I have multi-process application in which primary process initializes all c= rypto devices and sets up sessions. Secondary process uses the pre-initiali= zed devices and sessions. It was working fine till DPDK 18.05. When switched to DPDK 18.11, secondar= y 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 appli= cation works fine on DPDK 18.11. Is the usage model correct? Anything chan= ged in DPDK 18.11 which might explain this? Regards Pravin GDB backtrace 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_PROCE= SSED)) { [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)