From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] clocksource/drivers/timer-ti-dm: fix child node refcount handling
Date: Mon, 28 Oct 2024 13:26:43 +0100 [thread overview]
Message-ID: <e7ca7a5d-749d-40c1-893f-da3d593eb4d4@gmail.com> (raw)
In-Reply-To: <5a535983-6a78-4449-b57b-176869fd55d8@linaro.org>
On 28/10/2024 12:24, Daniel Lezcano wrote:
>
> Hi Javier,
>
> thanks for spotting the issue
>
>
> On 13/10/2024 12:14, Javier Carrasco wrote:
>> of_find_compatible_node() increments the node's refcount, and it must be
>> decremented again with a call to of_node_put() when the pointer is no
>> longer required to avoid leaking memory.
>>
>> Add the missing calls to of_node_put() in dmtimer_percpu_quirck_init()
>> for the 'arm_timer' device node.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: 25de4ce5ed02 ("clocksource/drivers/timer-ti-dm: Handle dra7
>> timer wrap errata i940")
>> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
>> ---
>> drivers/clocksource/timer-ti-dm-systimer.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/clocksource/timer-ti-dm-systimer.c b/drivers/
>> clocksource/timer-ti-dm-systimer.c
>> index c2dcd8d68e45..23be1d21ce21 100644
>> --- a/drivers/clocksource/timer-ti-dm-systimer.c
>> +++ b/drivers/clocksource/timer-ti-dm-systimer.c
>> @@ -691,8 +691,10 @@ static int __init
>> dmtimer_percpu_quirk_init(struct device_node *np, u32 pa)
>> arm_timer = of_find_compatible_node(NULL, NULL, "arm,armv7-timer");
>> if (of_device_is_available(arm_timer)) {
>> pr_warn_once("ARM architected timer wrap issue i940
>> detected\n");
>> + of_node_put(arm_timer);
>> return 0;
>> }
>> + of_node_put(arm_timer);
>
> Best practice would be to group of_node_put into a single place.
>
> bool available;
>
> [ ... ]
>
> available = of_device_is_available(arm_timer);
> of_node_put(arm_timer);
>
> if (available) {
> pr_warn_once("ARM architected timer wrap issue i940 detected\n");
> return 0;
> }
>
>
>> if (pa == 0x4882c000) /* dra7 dmtimer15 */
>> return dmtimer_percpu_timer_init(np, 0);
>>
>> ---
>> base-commit: d61a00525464bfc5fe92c6ad713350988e492b88
>> change-id: 20241013-timer-ti-dm-systimer-of_node_put-d42735687698
>>
>> Best regards,
>
>
Hi Daniel, thanks for your feedback.
Actually, if we are going to refactor the code, we would not need the
extra variable or even the call to of_node_put(), since we could use the
__free() macro. That would be a second patch after the fix, which could
stay as it is without refactoring, because it is only to backport the
missing calls to of_node_put().
I can send a v2 with the extra patch leaving this one as it is, or if
really desired, with the available variable.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2024-10-28 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 10:14 [PATCH] clocksource/drivers/timer-ti-dm: fix child node refcount handling Javier Carrasco
2024-10-28 11:24 ` Daniel Lezcano
2024-10-28 12:26 ` Javier Carrasco [this message]
2024-10-28 13:49 ` 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=e7ca7a5d-749d-40c1-893f-da3d593eb4d4@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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