All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liang He" <windhl@126.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: linux@armlinux.org.uk, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] arm/mach-omap2: Fix refcount leak bug in omap_hwmod.c
Date: Tue, 28 Jun 2022 13:51:50 +0800 (CST)	[thread overview]
Message-ID: <4b994fd6.3db9.181a8ddb1e9.Coremail.windhl@126.com> (raw)
In-Reply-To: <YrqKKBflkZKRHwXW@atomide.com>



At 2022-06-28 12:57:12, "Tony Lindgren" <tony@atomide.com> wrote:
>Hi,
>
>* Liang He <windhl@126.com> [220618 04:43]:
>> In _init(), of_find_node_by_name() will return a node pointer with
>> refcount incremented. We should use of_node_put() in fail path or
>> when it is not used anymore.
>> 
>> NOTE: As the ref will be passed from 'bus' to 'np' by the xx_lookup(),
>> in normal exit path, we should call of_node_put() at the end use of 'np',
>> not the end use of 'bus'.
>
>Looks correct to me. What about missing of_node_put() for
>of_get_next_child() also in the _init() function?
>
>Regards,
>
>Tony

Thanks, Tony.

I have found this bug but not send the patch for of_get_next_child()
as I am collecting other OF function related bugs and I have been told that it is better 
to collect all similar bugs in same directory, then finally report them.

So I will send a new patch for both of the two missing 'put' bugs caused by
of_find_xxx() and of_get_xxx() in omap_hwmod.c

Thanks gain.

Liang


WARNING: multiple messages have this Message-ID (diff)
From: "Liang He" <windhl@126.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: linux@armlinux.org.uk, linux-omap@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] arm/mach-omap2: Fix refcount leak bug in omap_hwmod.c
Date: Tue, 28 Jun 2022 13:51:50 +0800 (CST)	[thread overview]
Message-ID: <4b994fd6.3db9.181a8ddb1e9.Coremail.windhl@126.com> (raw)
In-Reply-To: <YrqKKBflkZKRHwXW@atomide.com>



At 2022-06-28 12:57:12, "Tony Lindgren" <tony@atomide.com> wrote:
>Hi,
>
>* Liang He <windhl@126.com> [220618 04:43]:
>> In _init(), of_find_node_by_name() will return a node pointer with
>> refcount incremented. We should use of_node_put() in fail path or
>> when it is not used anymore.
>> 
>> NOTE: As the ref will be passed from 'bus' to 'np' by the xx_lookup(),
>> in normal exit path, we should call of_node_put() at the end use of 'np',
>> not the end use of 'bus'.
>
>Looks correct to me. What about missing of_node_put() for
>of_get_next_child() also in the _init() function?
>
>Regards,
>
>Tony

Thanks, Tony.

I have found this bug but not send the patch for of_get_next_child()
as I am collecting other OF function related bugs and I have been told that it is better 
to collect all similar bugs in same directory, then finally report them.

So I will send a new patch for both of the two missing 'put' bugs caused by
of_find_xxx() and of_get_xxx() in omap_hwmod.c

Thanks gain.

Liang

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-28  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  1:47 [PATCH] arm/mach-omap2: Fix refcount leak bug in omap_hwmod.c Liang He
2022-06-18  1:47 ` Liang He
2022-06-22  9:00 ` Krzysztof Kozlowski
2022-06-22  9:00   ` Krzysztof Kozlowski
2022-06-28  4:57 ` Tony Lindgren
2022-06-28  4:57   ` Tony Lindgren
2022-06-28  5:51   ` Liang He [this message]
2022-06-28  5:51     ` Liang He
2022-06-28  6:04     ` Tony Lindgren
2022-06-28  6:04       ` Tony Lindgren

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=4b994fd6.3db9.181a8ddb1e9.Coremail.windhl@126.com \
    --to=windhl@126.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.