From: Manush Prajwal <manushprajwal555@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Manush Prajwal <manushprajwal555@gmail.com>
Subject: [PATCH] bus: arm-cci: fix device_node refcount leak in cci_probe_ports()
Date: Thu, 13 Aug 2026 16:40:14 +0530 [thread overview]
Message-ID: <20260813111014.895-1-manushprajwal555@gmail.com> (raw)
When the number of matching child nodes reaches nb_cci_ports,
cci_probe_ports() breaks out of the for_each_available_child_of_node()
loop without releasing the reference held on the current node. Every
other exit from this loop iteration either continues (handled by the
iterator) or stores the node into ports[i].dn; this early break is the
only path that drops the last handle to the node without a matching
of_node_put(). Add it before the break.
Signed-off-by: Manush Prajwal <manushprajwal555@gmail.com>
---
drivers/bus/arm-cci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
index 7f2baf0571..5ab3d74c9a 100644
--- a/drivers/bus/arm-cci.c
+++ b/drivers/bus/arm-cci.c
@@ -461,8 +461,10 @@ static int cci_probe_ports(struct device_node *np)
i = nb_ace + nb_ace_lite;
- if (i >= nb_cci_ports)
+ if (i >= nb_cci_ports) {
+ of_node_put(cp);
break;
+ }
if (of_property_read_string(cp, "interface-type",
&match_str)) {
--
2.46.2.windows.1
next reply other threads:[~2026-08-13 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:10 Manush Prajwal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-21 15:57 [PATCH] bus: arm-cci: fix device_node refcount leak in cci_probe_ports() Manush Prajwal
2026-08-24 7:00 ` Markus Elfring
2026-08-24 11:48 ` Robin Murphy
2026-08-24 12:00 ` Markus Elfring
2026-08-24 11:41 ` Robin Murphy
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=20260813111014.895-1-manushprajwal555@gmail.com \
--to=manushprajwal555@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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.