From: Thomas Gleixner <tglx@linutronix.de>
To: jackysliu <1972843537@qq.com>
Cc: linux-kernel@vger.kernel.org, Siyang Liu <1972843537@qq.com>
Subject: Re: [PATCH] irqchip/ls-extirq: fix resource leak in ls_extirq_parse_map()
Date: Mon, 21 Jul 2025 23:22:55 +0200 [thread overview]
Message-ID: <87bjpdtf0w.ffs@tglx> (raw)
In-Reply-To: <tencent_0A4AB3348A519A1A2EF46D99BF6A52D9BB06@qq.com>
On Mon, Jul 21 2025 at 12:43, jackysliu wrote:
> From: Siyang Liu <1972843537@qq.com>
>
> The ls_extirq_parse_map function uses of_find_node_by_phandle() to obtain
ls_extirq_parse_map() uses ...
> interrupt parent nodes within a loop, but fails to release the reference
> count on these nodes. This results in a kernel memory leak as the node
> reference counts continuously increase.
There is no continous increase as each ipar node is only looked up and
referenced exactly once. So this leaks exactly ONE reference count per
node.
> Add of_node_put() calls to properly release the references when the nodes
I see only one call, not several calls...
> are no longer needed
>
> Signed-off-by: Siyang Liu <1972843537@qq.com>
> ---
> drivers/irqchip/irq-ls-extirq.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/irqchip/irq-ls-extirq.c b/drivers/irqchip/irq-ls-extirq.c
> index 50a7b38381b9..fb4e7b3a6e2f 100644
> --- a/drivers/irqchip/irq-ls-extirq.c
> +++ b/drivers/irqchip/irq-ls-extirq.c
> @@ -164,6 +164,7 @@ ls_extirq_parse_map(struct ls_extirq_data *priv, struct device_node *node)
> for (j = 0; j < intsize; ++j)
> priv->map[hwirq].param[j] = be32_to_cpup(map++);
> mapsize -= intsize;
> + of_node_put(ipar);
That's the wrong point as this might not be reached because of the
following checks before the inner loop:
ret = of_property_read_u32(ipar, "#interrupt-cells", &intsize);
if (ret)
return ret;
if (intsize > mapsize)
return -EINVAL;
Please don't add put() calls in every error return path. _ONE_ put() at
the proper place is sufficient.
Thanks,
tglx
prev parent reply other threads:[~2025-07-21 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 4:43 [PATCH] irqchip/ls-extirq: fix resource leak in ls_extirq_parse_map() jackysliu
2025-07-21 21:22 ` Thomas Gleixner [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=87bjpdtf0w.ffs@tglx \
--to=tglx@linutronix.de \
--cc=1972843537@qq.com \
--cc=linux-kernel@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 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.