From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF28DC2B9F4 for ; Thu, 17 Jun 2021 14:20:44 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 502986135C for ; Thu, 17 Jun 2021 14:20:44 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 502986135C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 60EB44069C; Thu, 17 Jun 2021 16:20:43 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id BECCA40150; Thu, 17 Jun 2021 16:20:41 +0200 (CEST) IronPort-SDR: cAN5XHDxnWgBgOa66StJGtBxyMESxoT+2Ksoy+pgDjuXSTuqX4HsnYryjtNRso+GxWRIrutg3v AQ1/h7d2g8wQ== X-IronPort-AV: E=McAfee;i="6200,9189,10017"; a="206332023" X-IronPort-AV: E=Sophos;i="5.83,280,1616482800"; d="scan'208";a="206332023" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2021 07:20:40 -0700 IronPort-SDR: l8x5ZYTg5GM5VLGsPWZbdoLXwIfJuwsL9Kddia7alnSL1XSShqKePx+L4EwaUoHTBBgB8jHQ2U bW47RYlWWFyw== X-IronPort-AV: E=Sophos;i="5.83,280,1616482800"; d="scan'208";a="404951223" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.17.26]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 17 Jun 2021 07:20:39 -0700 Date: Thu, 17 Jun 2021 15:20:35 +0100 From: Bruce Richardson To: Kevin Laatz Cc: dev@dpdk.org, stable@dpdk.org Message-ID: References: <20210617141752.93312-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210617141752.93312-1-kevin.laatz@intel.com> 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" 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