From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Liang He <windhl@126.com>
Cc: john@phrozen.org, xkernel.wang@foxmail.com,
wangborong@cdjrlc.com, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: lantiq: falcon: Fix refcount leak bug in sysctrl
Date: Tue, 21 Jun 2022 17:15:33 +0200 [thread overview]
Message-ID: <20220621151533.GD12206@alpha.franken.de> (raw)
In-Reply-To: <20220617121958.4047910-1-windhl@126.com>
On Fri, Jun 17, 2022 at 08:19:58PM +0800, Liang He wrote:
> In ltq_soc_init(), of_find_compatible_node() will return a node pointer
> with refcount incremented. We should use of_node_put() when it is not
> used anymore.
>
> Signed-off-by: Liang He <windhl@126.com>
> ---
> arch/mips/lantiq/falcon/sysctrl.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/mips/lantiq/falcon/sysctrl.c b/arch/mips/lantiq/falcon/sysctrl.c
> index 5204fc6d6d50..1187729d8cbb 100644
> --- a/arch/mips/lantiq/falcon/sysctrl.c
> +++ b/arch/mips/lantiq/falcon/sysctrl.c
> @@ -208,6 +208,12 @@ void __init ltq_soc_init(void)
> of_address_to_resource(np_sysgpe, 0, &res_sys[2]))
> panic("Failed to get core resources");
>
> + of_node_put(np_status);
> + of_node_put(np_ebu);
> + of_node_put(np_sys1);
> + of_node_put(np_syseth);
> + of_node_put(np_sysgpe);
> +
> if ((request_mem_region(res_status.start, resource_size(&res_status),
> res_status.name) < 0) ||
> (request_mem_region(res_ebu.start, resource_size(&res_ebu),
> --
> 2.25.1
applied to mips-fixes.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-06-21 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 12:19 [PATCH] mips: lantiq: falcon: Fix refcount leak bug in sysctrl Liang He
2022-06-21 15:15 ` Thomas Bogendoerfer [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=20220621151533.GD12206@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wangborong@cdjrlc.com \
--cc=windhl@126.com \
--cc=xkernel.wang@foxmail.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