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 164BAA0C4D; Mon, 6 Sep 2021 03:38:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C48F740E32; Mon, 6 Sep 2021 03:38:20 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 2E4A840C35; Mon, 6 Sep 2021 03:38:18 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10098"; a="219913275" X-IronPort-AV: E=Sophos;i="5.85,271,1624345200"; d="scan'208";a="219913275" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2021 18:38:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.85,271,1624345200"; d="scan'208";a="501993159" Received: from fmsmsx604.amr.corp.intel.com ([10.18.126.84]) by fmsmga008.fm.intel.com with ESMTP; 05 Sep 2021 18:38:17 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) by fmsmsx604.amr.corp.intel.com (10.18.126.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Sun, 5 Sep 2021 18:38:16 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Mon, 6 Sep 2021 09:38:15 +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.012; Mon, 6 Sep 2021 09:38:15 +0800 From: "Zhang, Qi Z" To: Qiming Chen , "dev@dpdk.org" CC: "Wang, Haiyue" , "stable@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] net/ixgbe: fix hash handle leak Thread-Index: AQHXnmuh4O1MwduT2ECnfwVjgDTPrauWQrVg Date: Mon, 6 Sep 2021 01:38:15 +0000 Message-ID: <61fa515eee1248b3ab1f104fad924481@intel.com> References: <20210831132407.7481-1-chenqiming_huawei@163.com> In-Reply-To: <20210831132407.7481-1-chenqiming_huawei@163.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] net/ixgbe: fix hash handle leak 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: dev On Behalf Of Qiming Chen > Sent: Tuesday, August 31, 2021 9:24 PM > To: dev@dpdk.org > Cc: Wang, Haiyue ; Qiming Chen > ; stable@dpdk.org > Subject: [dpdk-dev] [PATCH] net/ixgbe: fix hash handle leak >=20 > In the ixgbe_fdir_filter_init and ixgbe_l2_tn_filter_init functions, afte= r the hash > handle is created, the handle is not released in subsequent abnormal bran= ches. >=20 > Fixes: 080e3c0ee989 ("net/ixgbe: store flow director filter") > Fixes: d0c0c416ef1f ("net/ixgbe: store L2 tunnel filter") > Cc: stable@dpdk.org >=20 > Signed-off-by: Qiming Chen Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi