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 20EFFA0548; Tue, 22 Jun 2021 22:59:13 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A78434003F; Tue, 22 Jun 2021 22:59:12 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id 1034C4003E; Tue, 22 Jun 2021 22:59:11 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id CA45ACC7; Tue, 22 Jun 2021 16:59:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 22 Jun 2021 16:59:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= xor2GaMbHkqsn41XX1ZJbJ+jLKIf4vucNfvR4YV/5to=; b=gYpQ+05ulWvRuLTf tXD34vBvQyz4HUzxGCND3BY5YfMgXW2G8T8QmLjsllCqpJJzgdhIoavsUFBGgkp9 su51fiLuyXFILFhvo38GQczrNkiWh6rZgtyESII83Kqkht1wakIgH6dLZtqi9/+q /GyRqABevfBOfjYpG1RccBKf3YhNojB4g5dMQuF6ae9Iq2Ts5qnVeJNcbc2T/9Pc 5A6HojPQlBUwBcICetD/d8CesC5m09d8yRzd3LPl1DUBvEHx+j7BhtoP+9fZ0OWz c/9Jlzxo8AdjiHz7YqDK3XVrNpEQkGX67vZC5H/Rf5fcw+tCCD18aUl+xcSHZ2HK vkc8LA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=xor2GaMbHkqsn41XX1ZJbJ+jLKIf4vucNfvR4YV/5 to=; b=fBaP+knfLYiR8Zha1P4OE3QdRUJk/2BD2i10zkoyUPIDgz2Ov+aHkQCLR Fgegg+w8kCtuNz4eQXaWnV1JHsXz9TCk/CvfVOGyC+f5+npcKODebS5aDSyzYL4V XAcG9hv/cR2IOR9pgv5ft3iQIwSfoWgP0jDFuK19nVT5rhEbqmzfyYAwMkDDyL6i AFd2YFwRDJcX/Alrwzs/EgXAnK90gCPcFKWHcxd973A4SjNxJh+x56ULyjtVEX5G WIimxI6ABl3Be/DoGJV3SyOn6AHJhUpWZPbtRPyNfHzN/sBcUkuDl5QDR+V1k4OP uusy0mNjPQIx/KB5sPh0uYD4poe7Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeeguddgudehgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 22 Jun 2021 16:59:08 -0400 (EDT) From: Thomas Monjalon To: Kevin Laatz Cc: dev@dpdk.org, stable@dpdk.org, Bruce Richardson Date: Tue, 22 Jun 2021 22:59:07 +0200 Message-ID: <2063657.Auc8LsEzUy@thomas> In-Reply-To: References: <20210617141752.93312-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] raw/ioat: fix memory leak in device configure 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" 17/06/2021 16:20, Bruce Richardson: > On Thu, Jun 17, 2021 at 02:17:52PM +0000, Kevin Laatz wrote: > > During device configure, memory is allocated for "hdl_ring_flags". In the > > event of another call to the device configure function (reconfigure), a > > memory leak would occur. This patch fixes the memory leak by free'ing the > > memory before reallocating it. > > > > Fixes: 245efe544d8e ("raw/ioat: report status of completed jobs") > > > > Signed-off-by: Kevin Laatz > > --- > > Thanks, Kevin. > Acked-by: Bruce Richardson Cc: stable@dpdk.org Applied, thanks