Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Manush Prajwal <manushprajwal555@gmail.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	sudeep.holla@kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bus: arm-cci: fix device_node refcount leak in cci_probe_ports()
Date: Mon, 24 Aug 2026 12:41:51 +0100	[thread overview]
Message-ID: <78f188cd-706b-42cf-82a1-527c1efefce1@arm.com> (raw)
In-Reply-To: <6a887550.f7f62383.10ed1b.5875@mx.google.com>

On 2026-08-21 4:57 pm, Manush Prajwal wrote:
> cci_probe_ports() has two device_node refcount bugs in its
> for_each_available_child_of_node() loop over "cp":
> 
>   - When the computed port index "i" reaches nb_cci_ports, the loop
>     breaks out without releasing the reference the iterator was
>     holding on "cp", leaking it.

Note that this could only happen if the DT is bogus and specifies more 
control interfaces than can physically exist. And even then, holding an 
extra reference to a child node doesn't do any harm, since a) we already 
hold a reference on the parent node, and b) it's not like you could 
remove the system interconnect at runtime anyway.

>   - When a port is successfully parsed, "cp" is stored into
>     ports[i].dn for later use, but the loop keeps iterating afterwards.
>     The next for_each_available_child_of_node() step puts the
>     reference on the previous "cp" to advance to the next sibling, so
>     the pointer saved in ports[i].dn is left referencing a node whose
>     reference was already dropped.

...and similarly this isn't a practical issue as we never dereference 
the saved pointers; they're only used for comparison, which in reality 
happens once in cci_ace_init_ports() immediately after this is done once 
. Plus we do already hold a reference on their parent node, and it's not 
like you could remove the system interconnect at runtime anyway ;)

> Rework the loop around for_each_available_child_of_node_scoped()
> so the iterator's reference is dropped automatically on every exit
> path, including the early break. Since a matched node is kept alive
> in ports[i].dn past the end of the loop, take an explicit reference
> with of_node_get() when storing it.

However, for the sake of good practice, just in case anyone were to try 
to copy this code as an example for something else, it seems like a 
reasonable cleanup to me.

Reviewed-by: Robin Murphy <robin.murphy@arm.com>

> Signed-off-by: Manush Prajwal <manushprajwal555@gmail.com>
> ---
>   drivers/bus/arm-cci.c | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
> index 000000000..000000000 100644
> --- a/drivers/bus/arm-cci.c
> +++ b/drivers/bus/arm-cci.c
> @@ -438,8 +438,7 @@
>   static int cci_probe_ports(struct device_node *np)
>   {
>   	struct cci_nb_ports const *cci_config;
>   	int ret, i, nb_ace = 0, nb_ace_lite = 0;
> -	struct device_node *cp;
>   	struct resource res;
>   	const char *match_str;
>   	bool is_ace;
> @@ -455,7 +455,7 @@ static int cci_probe_ports(struct device_node *np)
>   	if (!ports)
>   		return -ENOMEM;
> 
> -	for_each_available_child_of_node(np, cp) {
> +	for_each_available_child_of_node_scoped(np, cp) {
>   		if (!of_match_node(arm_cci_ctrl_if_matches, cp))
>   			continue;
> 
> @@ -498,7 +498,7 @@ static int cci_probe_ports(struct device_node *np)
>   			ports[i].type = ACE_LITE_PORT;
>   			++nb_ace_lite;
>   		}
> -		ports[i].dn = cp;
> +		ports[i].dn = of_node_get(cp);
>   	}
> 
>   	/*
> --
> 2.46.2.windows.1
> 



  parent reply	other threads:[~2026-08-24 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-13 11:10 Manush Prajwal

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=78f188cd-706b-42cf-82a1-527c1efefce1@arm.com \
    --to=robin.murphy@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=manushprajwal555@gmail.com \
    --cc=sudeep.holla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox