mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <linmq006@gmail.com>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>, <Mihai.Sain@microchip.com>,
	<sudeep.holla@arm.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drivers: soc: atmel: Fix refcount leak in atmel_soc_device_init
Date: Tue, 7 Jun 2022 05:01:44 +0000	[thread overview]
Message-ID: <80d1d3f1-e168-1e6e-4020-acd3e4bdef1b@microchip.com> (raw)
In-Reply-To: <20220607030058.53695-1-linmq006@gmail.com>

On 07.06.2022 06:00, Miaoqian Lin wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> of_find_node_by_path() returns a node pointer with refcount incremented,
> we should use of_node_put() on it when not need anymore.
> Add missing of_node_put() to avoid refcount leak.
> 
> Fixes: 960ddf70cc11 ("drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs")
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>


> ---
> changes in v2:
> - create new variable match to refactor the patch.
> 
> v1 Link: https://lore.kernel.org/r/20220605084035.27127-1-linmq006@gmail.com
> ---
>  drivers/soc/atmel/soc.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/soc/atmel/soc.c b/drivers/soc/atmel/soc.c
> index b2d365ae0282..7152a38c657a 100644
> --- a/drivers/soc/atmel/soc.c
> +++ b/drivers/soc/atmel/soc.c
> @@ -368,8 +368,11 @@ static const struct of_device_id at91_soc_allowed_list[] __initconst = {
>  static int __init atmel_soc_device_init(void)
>  {
>         struct device_node *np = of_find_node_by_path("/");
> +       const struct of_device_id *match;
> 
> -       if (!of_match_node(at91_soc_allowed_list, np))
> +       match = of_match_node(at91_soc_allowed_list, np);
> +       of_node_put(np);
> +       if (!match)
>                 return 0;
> 
>         at91_soc_init(socs);
> --
> 2.25.1
> 


      reply	other threads:[~2022-06-07  5:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  3:00 Miaoqian Lin
2022-06-07  5:01 ` Claudiu.Beznea [this message]

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=80d1d3f1-e168-1e6e-4020-acd3e4bdef1b@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Mihai.Sain@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linmq006@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    /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®