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 AE3FBA0C4D; Mon, 6 Sep 2021 03:45:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3CCD940E32; Mon, 6 Sep 2021 03:45:14 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mails.dpdk.org (Postfix) with ESMTP id 1005940C35; Mon, 6 Sep 2021 03:45:11 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10098"; a="216701302" X-IronPort-AV: E=Sophos;i="5.85,271,1624345200"; d="scan'208";a="216701302" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2021 18:45:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.85,271,1624345200"; d="scan'208";a="430401934" Received: from fmsmsx601.amr.corp.intel.com ([10.18.126.81]) by orsmga003.jf.intel.com with ESMTP; 05 Sep 2021 18:45:10 -0700 Received: from shsmsx606.ccr.corp.intel.com (10.109.6.216) by fmsmsx601.amr.corp.intel.com (10.18.126.81) 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:45:08 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX606.ccr.corp.intel.com (10.109.6.216) 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:45:06 +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:45:06 +0800 From: "Zhang, Qi Z" To: "Wang, Haiyue" , Qiming Chen , "dev@dpdk.org" CC: "stable@dpdk.org" Thread-Topic: [PATCH v3] net/ixgbe: fix mbuf leak Thread-Index: AQHXor21i2qddYqE4E+/8/fWtuUuZauWPBfA Date: Mon, 6 Sep 2021 01:45:06 +0000 Message-ID: <4a45f9ecdb0544d5af3ed22d8a98c2bd@intel.com> References: <20210831080630.5719-1-chenqiming_huawei@163.com> <20210901072237.9451-1-chenqiming_huawei@163.com> In-Reply-To: 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 v3] net/ixgbe: fix mbuf 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 Wang, Haiyue > Sent: Monday, September 6, 2021 9:22 AM > To: Qiming Chen ; dev@dpdk.org > Cc: stable@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3] net/ixgbe: fix mbuf leak >=20 > > -----Original Message----- > > From: Qiming Chen > > Sent: Wednesday, September 1, 2021 15:23 > > To: dev@dpdk.org > > Cc: Wang, Haiyue ; Qiming Chen > > ; stable@dpdk.org > > Subject: [PATCH v3] net/ixgbe: fix mbuf leak > > > > A local test found that repeated port start and stop operations during > > the continuous SSE vector bufflist receiving process will cause the > > mbuf resource to run out. The final positioning is when the port is > > stopped, the mbuf of the pkt_first_seg pointer is not released. Resourc= es > leak. > > The patch scheme is to judge whether the pointer is empty when the > > port is stopped, and release the corresponding mbuf if it is not empty. > > > > Fixes: af75078fece3 ("first public release") > > Cc: stable@dpdk.org > > > > Signed-off-by: Qiming Chen > > --- > > v2: > > Sync to stable@dpdk.org > > v3: > > Modify fixes commit > > --- > > drivers/net/ixgbe/ixgbe_rxtx.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > >=20 > Acked-by: Haiyue Wang Applied to dpdk-next-net-intel. Thanks Qi >=20 >=20 > > > > -- > > 2.30.1.windows.1