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 AF750A0093 for ; Wed, 11 May 2022 02:04:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A84264113D; Wed, 11 May 2022 02:04:35 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id E4F4D4067E; Wed, 11 May 2022 02:04:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652227473; x=1683763473; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=k8FwnELuQgVqts2D3UkQDgjOgPKg0yyb2sfgU4aFe08=; b=OnB00JrSsya+yASjkHJlP1fYn78MfoK73W6SLDWiHTq/DEM16Aa1+ZIg GhSApt8FB3UBPfJzI3Yuz+2YbtgSOm/Phyp74U5mrXplpD7/G7ffRWgVJ Mj04svhAgrP+b3NEWNTaZ+vA43+u1nd/gHEUmkbltCTFixY/8HKUSd6NT InAL1A1GGqu0ltWcnnpLaGQB4H1oQULnbECl1qOpmws4qouAiexWRVesp HgbEvIJpG6mX+xI3KGO6DVj57pjPFA6zoMwI4RWMEVcOVm1CLYbHqlyec ZebEs0/a4hwoZsdW3yMYAaJ8q8JIgPr4gzAZa7TdUSytzyUqM1v96tLP/ A==; X-IronPort-AV: E=McAfee;i="6400,9594,10343"; a="269471154" X-IronPort-AV: E=Sophos;i="5.91,215,1647327600"; d="scan'208";a="269471154" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 May 2022 17:04:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,215,1647327600"; d="scan'208";a="657891339" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by FMSMGA003.fm.intel.com with ESMTP; 10 May 2022 17:04:26 -0700 Received: from fmsmsx610.amr.corp.intel.com (10.18.126.90) by fmsmsx602.amr.corp.intel.com (10.18.126.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27; Tue, 10 May 2022 17:04:26 -0700 Received: from fmsmsx612.amr.corp.intel.com (10.18.126.92) by fmsmsx610.amr.corp.intel.com (10.18.126.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27; Tue, 10 May 2022 17:04:25 -0700 Received: from fmsmsx612.amr.corp.intel.com ([10.18.126.92]) by fmsmsx612.amr.corp.intel.com ([10.18.126.92]) with mapi id 15.01.2308.027; Tue, 10 May 2022 17:04:25 -0700 From: "Zhang, Qi Z" To: "Zhang, Qi Z" , "Zhou, YidingX" , "dev@dpdk.org" , "Wu, Jingjing" , "Xing, Beilei" CC: "Yang, Qiming" , "stable@dpdk.org" , "Yeleswarapu, Ramamani" Subject: RE: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and RX descriptor Thread-Topic: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and RX descriptor Thread-Index: AQHYYggIymU26kq8NEGZQYZlYRLD8K0VzaJwgAMDIBA= Date: Wed, 11 May 2022 00:04:25 +0000 Message-ID: References: <20220507093637.127591-1-yidingx.zhou@intel.com> <20220507195239.250067-1-yidingx.zhou@intel.com> <16094f5ab1604c06bcf7ad322a649ebc@intel.com> In-Reply-To: <16094f5ab1604c06bcf7ad322a649ebc@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.6.401.20 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org > -----Original Message----- > From: Zhang, Qi Z > Sent: Monday, May 9, 2022 10:05 AM > To: Zhou, YidingX ; dev@dpdk.org; Wu, Jingjing > ; Xing, Beilei > Cc: Yang, Qiming ; stable@dpdk.org; Yeleswarapu, > Ramamani > Subject: RE: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and R= X > descriptor >=20 >=20 >=20 > > -----Original Message----- > > From: Zhou, YidingX > > Sent: Sunday, May 8, 2022 3:53 AM > > To: dev@dpdk.org; Wu, Jingjing ; Xing, Beilei > > > > Cc: Yang, Qiming ; Zhang, Qi Z > > ; stable@dpdk.org; Yeleswarapu, Ramamani > > > > Subject: [PATCH v2] net/iavf: fix mismatch between rx_pkt_burst and RX > > descriptor Refined the title to " fix wrong data path selection which cause segment fa= ult"=20 In dpdk-next-net-intel to make it clear what it is going to fix. > > > > Some kernel drivers return the capability > > VIRTCHNL_VF_OFFLOAD_RX_FLEX_DESC when IAVF_RXDID_COMMS_OVS_1 > is not > > supported. This causes PMD to use rx_pkt_burst that handles the Flex > > Receive Descriptor format, but actually configures the RXDID into > > IAVF_RXDID_LEGACY_1, then the fields of rte_mbuf Will be filled with > > wrong values in rx_pkt_burst, which will eventually lead to coredump. > > > > This patch fixes mismatch between rx_pkt_burst and rx descriptor. > > > > Fixes: 12b435bf8f2f ("net/iavf: support flex desc metadata > > extraction") > > Cc: stable@dpdk.org > > > > Signed-off-by: Yiding Zhou >=20 > Acked-by: Qi Zhang >=20 > Applied to dpdk-next-net-intel. >=20 > Thanks > Qi