From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Sunny <nueralspacetech@gmail.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: Fix reference leak in of_i2c_register_devices
Date: Tue, 8 Apr 2025 21:04:16 +0200 [thread overview]
Message-ID: <1dacfce7-c66d-44c6-9a0c-2dd00bc24ffc@wanadoo.fr> (raw)
In-Reply-To: <CAGNPQObiZA76gva-+_DY8TtpEiJfLL3QDoONYST4npOSkgZ+5g@mail.gmail.com>
Hi,
first of all, you should not reply with HTML mail, because most mailing
lists reject such messages.
Le 08/04/2025 à 16:01, Sunny a écrit :
> To clarify, while there is no early exit path in the
> for_each_available_child_of_node() loop, the reference leak can still
> occur because the macro increments the reference count for each node
> it processes. If i2c_new_client_device() fails, the reference count
> for that node must be explicitly decremented using of_node_put(node).
> Without this, the reference count remains elevated, leading to a
> reference leak.
I think you are wrong.
Yes, for_each_available_child_of_node() increments the reference count
for each node it processes, but it also decrements it at the end of the
iteration, except when there is an early exit (a break or a return).
See how the 'parent' and 'child' parameters of
of_get_next_available_child() are used, especially whtat happen with the
first call with child = NULL.
So should i2c_new_client_device() fail or succeed, 'node' is released
and the reference count does NOT remain elevated as you state.
If you do not agree, please give more details of how you think it works
and where the issue is, for exemple with unrolling the loop and noting
what and when nodes are get and put.
You should then see that it is correct.
The of_node_put(node) you are looking for is there:
https://elixir.bootlin.com/linux/v6.14-rc6/source/drivers/of/base.c#L702
CJ
>
> sunny
>
> On Sun, 6 Apr 2025 at 23:36, Christophe JAILLET
> <christophe.jaillet@wanadoo.fr> wrote:
>
> Le 06/04/2025 à 15:48, Sunny Patel a écrit :
> > Fix a potential reference leak in of_i2c_register_devices where the
> > reference to the node is not released if device registration fails.
> > This ensures proper reference management and avoids memory leaks.
>
> There is no early exit path in the for_each_available_child_of_node()
> block, so of_node_put((node) is called for all the nodes that are
> iterated.
>
> Can you elaborate and explain how the reference leak can occur?
>
> CJ
>
> >
> > Signed-off-by: Sunny Patel <nueralspacetech@gmail.com>
> > ---
> > drivers/i2c/i2c-core-of.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/i2c/i2c-core-of.c b/drivers/i2c/i2c-core-of.c
> > index 02feee6c9ba9..7c50905de8f1 100644
> > --- a/drivers/i2c/i2c-core-of.c
> > +++ b/drivers/i2c/i2c-core-of.c
> > @@ -107,6 +107,7 @@ void of_i2c_register_devices(struct
> i2c_adapter *adap)
> > "Failed to create I2C device for
> %pOF\n",
> > node);
> > of_node_clear_flag(node, OF_POPULATED);
> > + of_node_put(node);
> > }
> > }
> >
>
next prev parent reply other threads:[~2025-04-08 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 13:48 [PATCH] i2c: Fix reference leak in of_i2c_register_devices Sunny Patel
2025-04-06 18:06 ` Christophe JAILLET
[not found] ` <CAGNPQObiZA76gva-+_DY8TtpEiJfLL3QDoONYST4npOSkgZ+5g@mail.gmail.com>
2025-04-08 19:04 ` Christophe JAILLET [this message]
2025-04-14 15:42 ` Sunny Patel
2025-04-16 22:11 ` Christophe JAILLET
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=1dacfce7-c66d-44c6-9a0c-2dd00bc24ffc@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nueralspacetech@gmail.com \
--cc=wsa+renesas@sang-engineering.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