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 59C5FA034F; Mon, 7 Jun 2021 02:42:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CA65640041; Mon, 7 Jun 2021 02:42:21 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mails.dpdk.org (Postfix) with ESMTP id E8A8F4003E; Mon, 7 Jun 2021 02:42:19 +0200 (CEST) IronPort-SDR: oivnp84nEh6fZ5YaL7RwlmBPdaji6utOYUD0lpfpI6ukudIUtYXvyhTRdVFHKFNauqXfuazhHs VjU/s0tbcIkw== X-IronPort-AV: E=McAfee;i="6200,9189,10007"; a="184914087" X-IronPort-AV: E=Sophos;i="5.83,254,1616482800"; d="scan'208";a="184914087" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2021 17:42:17 -0700 IronPort-SDR: omUzKf6m/qXa16HbGePxi1kF1ddOB4OpTLv8LkeIwHfd8DvA3nAxnGnQ1YnUTNY52DO3g76tLP g4xzqgEMPW9w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.83,254,1616482800"; d="scan'208";a="551727569" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by fmsmga001.fm.intel.com with ESMTP; 06 Jun 2021 17:42:17 -0700 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) 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.2242.4; Sun, 6 Jun 2021 17:42:16 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX605.ccr.corp.intel.com (10.109.6.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.4; Mon, 7 Jun 2021 08:42:09 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2242.008; Mon, 7 Jun 2021 08:42:09 +0800 From: "Zhang, Qi Z" To: "Xu, Ting" , "dev@dpdk.org" CC: "Yang, Qiming" , "stable@dpdk.org" Thread-Topic: [PATCH v1] net/ice: fix wrong FDIR flow type for IPv4 fragment Thread-Index: AQHXV4fHwgEy66vT/0Cdx1B3Dv5pJqsHvKdQ Date: Mon, 7 Jun 2021 00:42:09 +0000 Message-ID: References: <20210602082104.33681-1-ting.xu@intel.com> In-Reply-To: <20210602082104.33681-1-ting.xu@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.5.1.3 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 Subject: Re: [dpdk-dev] [PATCH v1] net/ice: fix wrong FDIR flow type for IPv4 fragment 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 Sender: "dev" > -----Original Message----- > From: Xu, Ting > Sent: Wednesday, June 2, 2021 4:21 PM > To: dev@dpdk.org > Cc: Zhang, Qi Z ; Yang, Qiming > ; Xu, Ting ; stable@dpdk.org > Subject: [PATCH v1] net/ice: fix wrong FDIR flow type for IPv4 fragment >=20 > When creating FDIR rule and parsing the pattern, if IPv4 fragment type is > detected, the flow type is not changed to ICE_FLTR_PTYPE_FRAG_IPV4 from > ICE_FLTR_PTYPE_NONF_IPV4_OTHER. It will cause profile confilict with othe= r > FDIR rules for IPv4 other type. >=20 > Fixes: b7e8781de768 ("net/ice: support flow director for IP fragment pack= et") > Cc: stable@dpdk.org >=20 > Signed-off-by: Ting Xu Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi