From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 93AE2A0583; Fri, 20 Mar 2020 01:37:39 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 853041C025; Fri, 20 Mar 2020 01:37:38 +0100 (CET) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 0F90529D6 for ; Fri, 20 Mar 2020 01:37:35 +0100 (CET) IronPort-SDR: 057/AIhIkoMg0tOJiFkHSNCoCGR1NLo9Zj6tPVXu+xOs8HI7XI7nwA72hdhf1Be7YNkmX59nkk MMaCATPzfAcw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Mar 2020 17:37:34 -0700 IronPort-SDR: uGJC1QaT3yoqfRQB7RuXByoZLWmbZFXDtNCi7f7dP6fq51slCAZt1ihigknRkIjOmVm9PTl0B3 kMHnZumX9Ilw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,573,1574150400"; d="scan'208,217";a="268918055" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga004.fm.intel.com with ESMTP; 19 Mar 2020 17:37:34 -0700 Received: from shsmsx602.ccr.corp.intel.com (10.109.6.142) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 19 Mar 2020 17:37:34 -0700 Received: from shsmsx602.ccr.corp.intel.com (10.109.6.142) by SHSMSX602.ccr.corp.intel.com (10.109.6.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 20 Mar 2020 08:37:32 +0800 Received: from shsmsx602.ccr.corp.intel.com ([10.109.6.142]) by SHSMSX602.ccr.corp.intel.com ([10.109.6.142]) with mapi id 15.01.1713.004; Fri, 20 Mar 2020 08:37:32 +0800 From: "Zhao, XinfengX" To: "dev@dpdk.org" Thread-Topic: dpdk-dev] [PATCH] cryptodev: fix missing device id range checking Thread-Index: AdX9jW4ZBaPk2hSQSvq8ZRUhTlrVqQAwj6Pw Date: Fri, 20 Mar 2020 00:37:32 +0000 Message-ID: <99d93b95ec514defb664b15305fe073c@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.36] 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: Re: [dpdk-dev] dpdk-dev] [PATCH] cryptodev: fix missing device id range checking X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" Tested-by: Zhao, Xinfeng> > -----Original Message----- > From: Dybkowski, AdamX > > Sent: Thursday, February 20, 2020 3:04 PM > To: dev at dpdk.org; Trahe, Fiona >; akhil.goyal = at nxp.com > Cc: Dybkowski, AdamX >; stable at dpdk.org > Subject: [PATCH] cryptodev: fix missing device id range checking > > This patch adds range-checking of the device id passed from > the user app code. It prevents out-of-range array accesses > which in some situations resulted in an > application crash (segfault). > > Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id") > Cc: stable at dpdk.org > > Signed-off-by: Adam Dybkowski >