From: "J, KEERTHY" <j-keerthy@ti.com>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
Weigang He <geoffreyhe2@gmail.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Eduardo Valentin <edubezval@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] thermal/drivers/ti-soc-thermal: Cancel pending alert work on remove
Date: Tue, 29 Sep 2026 08:08:48 +0000 [thread overview]
Message-ID: <56fa2a1273ec4be0b8bb91afa04e4e61@ti.com> (raw)
In-Reply-To: <4005518f-5ca7-4849-a256-5c3fd481f2f0@oss.qualcomm.com>
-----Original Message-----
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
Sent: Tuesday, September 29, 2026 12:45 PM
To: Weigang He <geoffreyhe2@gmail.com>; Daniel Lezcano <daniel.lezcano@kernel.org>; Rafael J . Wysocki <rafael@kernel.org>; Eduardo Valentin <edubezval@gmail.com>; J, KEERTHY <j-keerthy@ti.com>
Cc: Zhang Rui <rui.zhang@intel.com>; Lukasz Luba <lukasz.luba@arm.com>; linux-pm@vger.kernel.org; linux-omap@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal/drivers/ti-soc-thermal: Cancel pending alert work on remove
On 9/26/26 14:49, Weigang He wrote:
> On a threshold crossing, the talert IRQ handler calls
> ti_thermal_report_sensor_temperature(), which queues the work embedded
> in the sensor's ti_thermal_data on the system workqueue. Nothing ever
> cancels or flushes that work.
>
> ti_bandgap_remove() frees the talert IRQ last. free_irq() waits for a
> running handler, but not for the work the handler has queued. When
> remove returns, devres unregisters and frees the thermal zones and
> then frees the devm-allocated ti_thermal_data, so a work item that is
> still pending runs ti_thermal_work() on freed memory:
>
> ti_thermal_work()
> data = container_of(work, struct ti_thermal_data, thermal_wq);
> thermal_zone_device_update(data->ti_thermal, ...);
>
> Free the talert IRQ before removing the sensors, so that no new work
> can be queued, and cancel the work in ti_thermal_remove_sensor().
>
> This needs an OMAP4460/4470 or OMAP5 SoC (DRA7 has TALERT but no
> ->report_temperature, so it never queues the work), a threshold
> ->crossing
> just before the driver is unbound or unloaded, and the work still
> pending when devres frees the data.
>
> Found by static analysis tool CodeQL.
>
> Fixes: 445eaf871bf9 ("staging: omap-thermal: common code to expose
> driver to thermal framework")
> Assisted-by: LLM codeql
> Signed-off-by: Weigang He <geoffreyhe2@gmail.com>
> ---
Sounds correct to me, so if nobody is against this change I'll apply it
> FWIW: Acked-by: Keerthy <j-keerthy@ti.com>
Thanks
prev parent reply other threads:[~2026-09-29 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 12:49 Weigang He
2026-09-29 7:15 ` Daniel Lezcano
2026-09-29 8:08 ` J, KEERTHY [this message]
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=56fa2a1273ec4be0b8bb91afa04e4e61@ti.com \
--to=j-keerthy@ti.com \
--cc=daniel.lezcano@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=edubezval@gmail.com \
--cc=geoffreyhe2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®