mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David E. Box" <david.e.box@linux.intel.com>
To: Dongliang Mu <dzm91@hust.edu.cn>,
	Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next 2/3] drivers/platform/x86/intel: fix a memory leak in intel_vsec_add_aux
Date: Wed, 08 Mar 2023 10:12:20 -0800	[thread overview]
Message-ID: <702721b279dd864db1b8ea468136b96075df3994.camel@linux.intel.com> (raw)
In-Reply-To: <20230308135538.479223-2-dzm91@hust.edu.cn>

Hi Dongliang,

Thanks for your patch. Do cc the mailing list next time.

Reviewed-by: David E. Box <david.e.box@linux.intel.com>

On Wed, 2023-03-08 at 21:55 +0800, Dongliang Mu wrote:
> The first error handling code in intel_vsec_add_aux misses the
> deallocation of intel_vsec_dev->resource.
> 
> Fix this by adding kfree(intel_vsec_dev->resource) in the error handling
> code.
> 
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> ---
>  drivers/platform/x86/intel/vsec.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/x86/intel/vsec.c
> b/drivers/platform/x86/intel/vsec.c
> index 13decf36c6de..2311c16cb975 100644
> --- a/drivers/platform/x86/intel/vsec.c
> +++ b/drivers/platform/x86/intel/vsec.c
> @@ -154,6 +154,7 @@ int intel_vsec_add_aux(struct pci_dev *pdev, struct device
> *parent,
>         ret = ida_alloc(intel_vsec_dev->ida, GFP_KERNEL);
>         mutex_unlock(&vsec_ida_lock);
>         if (ret < 0) {
> +               kfree(intel_vsec_dev->resource);
>                 kfree(intel_vsec_dev);
>                 return ret;
>         }


           reply	other threads:[~2023-03-08 18:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230308135538.479223-2-dzm91@hust.edu.cn>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=702721b279dd864db1b8ea468136b96075df3994.camel@linux.intel.com \
    --to=david.e.box@linux.intel.com \
    --cc=dzm91@hust.edu.cn \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®