From: Lukasz Luba <lukasz.luba@arm.com>
To: Sumeet Pawnikar <sumeet4linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
linux-pm@vger.kernel.org, rui.zhang@intel.com,
daniel.lezcano@kernel.org
Subject: Re: [PATCH] thermal: gov_power_allocator: Fix NULL pointer dereference in update_tz()
Date: Mon, 7 Sep 2026 08:51:19 +0100 [thread overview]
Message-ID: <3284bfcb-2dd9-4ca2-be08-c7ecc7571695@arm.com> (raw)
In-Reply-To: <20260822114236.15998-1-sumeet4linux@gmail.com>
On 8/22/26 12:42, Sumeet Pawnikar wrote:
> power_allocator_update_tz() unconditionally derives the trip descriptor of
> params->trip_max as below,
> const struct thermal_trip_desc *td = trip_to_trip_desc(params->trip_max);
> and then walks td->thermal_instances. However, params->trip_max is allowed
> to be NULL and in that case the list walk dereferences a bogus pointer
> derived from NULL which oops the kernel.
>
> get_governor_trips() picks trip_switch_on and trip_max out of the trip
> table of the zone. When the zone has neither a passive nor an active trip
> point, last_active is NULL and params->trip_max is left NULL. This is an
> explicitly supported configuration, as documented in the function
> get_governor_trips() as below,
> If there are no passive or active trip points, then the governor won't
> do anything. In fact, its throttle function won't be called at all.
>
> Return early from power_allocator_update_tz() when params->trip_max is NULL
> and only compute the trip descriptor after that check. There is nothing to
> update in that case anyway, with no trip_max and there are no thermal
> instances for the governor to account for, num_actors stays zero and
> total_weight is irrelevant.
>
> Fixes: 912e97c67cc3 ("thermal: gov_power_allocator: Move memory allocation out of throttle()")
>
> Signed-off-by: Sumeet Pawnikar <sumeet4linux@gmail.com>
> ---
> drivers/thermal/gov_power_allocator.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/gov_power_allocator.c b/drivers/thermal/gov_power_allocator.c
> index 37f2e22a999e..b5c254187628 100644
> --- a/drivers/thermal/gov_power_allocator.c
> +++ b/drivers/thermal/gov_power_allocator.c
> @@ -660,10 +660,15 @@ static void power_allocator_update_tz(struct thermal_zone_device *tz,
> enum thermal_notify_event reason)
> {
> struct power_allocator_params *params = tz->governor_data;
> - const struct thermal_trip_desc *td = trip_to_trip_desc(params->trip_max);
> + const struct thermal_trip_desc *td;
> struct thermal_instance *instance;
> int num_actors = 0;
>
> + if (!params->trip_max)
> + return;
> +
> + td = trip_to_trip_desc(params->trip_max);
> +
> switch (reason) {
> case THERMAL_TZ_BIND_CDEV:
> case THERMAL_TZ_UNBIND_CDEV:
LGTM,
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2026-09-07 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 11:42 [PATCH] thermal: gov_power_allocator: Fix NULL pointer dereference in update_tz() Sumeet Pawnikar
2026-09-07 7:51 ` Lukasz Luba [this message]
2026-09-11 13:43 ` Rafael J. Wysocki (Intel)
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=3284bfcb-2dd9-4ca2-be08-c7ecc7571695@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sumeet4linux@gmail.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