From: "Liang He" <windhl@126.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Amit Kucheria" <amitk@kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
"Linux PM" <linux-pm@vger.kernel.org>
Subject: Re:Re: [PATCH] thermal/core: Fix refcount bugs in __thermal_cooling_device_register()
Date: Sat, 16 Jul 2022 10:00:41 +0800 (CST) [thread overview]
Message-ID: <4e28500a.6b9.18204bc8cd3.Coremail.windhl@126.com> (raw)
In-Reply-To: <CAJZ5v0iOF3n98byY5C4zAjM=AbxDiUHF9vqEp78i6_jg8M5MqQ@mail.gmail.com>
At 2022-07-16 01:14:31, "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>On Thu, Jul 7, 2022 at 8:21 AM Liang He <windhl@126.com> wrote:
>>
>> For each new reference of 'device_node', we should increase its
>> refcount. Otherwise, there will be premature free.
>>
>> For example, in drivers\thermal\tegra\soctherm.c, the function
>> soctherm_init_hw_throt_cdev() will use for_each_child_of_node() to
>> iterate its child device_node which will be then passed into
>> __thermal_cooling_device_register(). As for_each_xxx OF APIs will
>> automatically increase and decrease the refcount of 'device_node',
>> we should use additional of_node_get() to record the new refernece.
>
>reference
Thanks!
>
>>
>> NOTE, we should also call the corresponding of_node_put() in fail path
>> or when the *_unregister() function is called.
>
>The NOTE in capitals above is somewhat confusing. I would just say
>"Accordingly, the corresponding of_node_put() needs to be run in the
>error code path and on cooling device unregistration."
>
Thanks, I will change that in new version.
>>
>> Fixes: a116b5d44f14 ("thermal: core: introduce thermal_of_cooling_device_register")
>> Signed-off-by: Liang He <windhl@126.com>
>> ---
>> I cannot confirm, in *_unregister, we should put of_node_put() in or
>> out of the *_lock/*_unlock functions. Please check it carefully.
>
>This doesn't matter too much AFAICS.
>
>Please note that the of_node_put() can still "leak" into the critical
>section through the "unlock" operation, because the latter is not a
>full memory barrier.
>
>Moreover, dropping the reference means that the object in question
>won't be used any more by the holder of that reference and it is no
>reason I can see why it would be necessary to hold the lock while
>doing that.
>
>> drivers/thermal/thermal_core.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
>> index cdc0552e8c42..c459e2958b7b 100644
>> --- a/drivers/thermal/thermal_core.c
>> +++ b/drivers/thermal/thermal_core.c
>> @@ -919,7 +919,7 @@ __thermal_cooling_device_register(struct device_node *np,
>>
>> mutex_init(&cdev->lock);
>> INIT_LIST_HEAD(&cdev->thermal_instances);
>> - cdev->np = np;
>> + cdev->np = of_node_get(np);
>> cdev->ops = ops;
>> cdev->updated = false;
>> cdev->device.class = &thermal_class;
>> @@ -947,6 +947,7 @@ __thermal_cooling_device_register(struct device_node *np,
>> return cdev;
>>
>> out_kfree_type:
>> + of_node_put(cdev->np);
>> thermal_cooling_device_destroy_sysfs(cdev);
>> kfree(cdev->type);
>> put_device(&cdev->device);
>> @@ -1111,6 +1112,7 @@ void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev)
>>
>> mutex_unlock(&thermal_list_lock);
>>
>> + of_node_put(cdev->np);
>
>Could this be done right before the
>thermal_cooling_device_destroy_sysfs() below? Then the sequence would
>be completely analogous to the error code path above.
>
That souds good, I will change it in new version.
>> ida_simple_remove(&thermal_cdev_ida, cdev->id);
>> device_del(&cdev->device);
>> thermal_cooling_device_destroy_sysfs(cdev);
>> --
>
>Overall, this looks like a genuine fix to me.
>
>Daniel, what do you think?
I will also wait Daniel's reponse before I send new version.
Thanks again,
Liang
next prev parent reply other threads:[~2022-07-16 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 6:21 [PATCH] thermal/core: Fix refcount bugs in __thermal_cooling_device_register() Liang He
2022-07-15 17:14 ` Rafael J. Wysocki
2022-07-16 2:00 ` Liang He [this message]
2022-07-16 22:03 ` Daniel Lezcano
2022-07-17 2:57 ` Liang He
2022-07-17 7:06 ` Daniel Lezcano
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=4e28500a.6b9.18204bc8cd3.Coremail.windhl@126.com \
--to=windhl@126.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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 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.