From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Christian Schmidbauer <opensource@grische.xyz>,
Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] thermal/drivers/qcom/tsens: Drop __init from the ->init callbacks
Date: Wed, 4 Nov 2026 16:33:40 +0100 [thread overview]
Message-ID: <98d01186-7d87-459e-8c18-db201baef34a@oss.qualcomm.com> (raw)
In-Reply-To: <20261104145740.2623473-1-opensource@grische.xyz>
Hi Christian,
I don't see the patches along with the cover letter
On 11/4/26 15:57, Christian Schmidbauer wrote:
> Every function that tsens_probe() calls through priv->ops->init() is
> marked __init, so a probe after free_initmem() jumps into freed memory.
> On IPQ8064 with CONFIG_IPQ_LCC_806X disabled, fw_devlink defers the
> probe of gcc and its tsens child until the deferred probe timeout,
> which expires after init memory is freed. On an Aruba AP-325 the probe
> then crashes in init_common(). With CONFIG_QCOM_TSENS=m the driver has
> the same problem once the module's init function has returned.
>
> Patch 1 drops __init from init_common() in a one-line change that
> applies to every stable tree. Patch 2 drops it from the eight per-SoC
> callbacks.
>
> Patch 1 was tested on an Aruba AP-325 on a v7.2-rc7 based tree.
>
> Not tested:
> - Patch 2 on hardware. None of msm8226, msm8909, msm8939, msm8952,
> msm8956, mdm9607, ipq5018, ipq5332 or ipq5424 was available, so patch
> 2 is only compile-tested.
> - CONFIG_QCOM_TSENS=m on hardware.
>
> Christian Schmidbauer (2):
> thermal/drivers/qcom/tsens: Drop __init from init_common()
> thermal/drivers/qcom/tsens: Drop __init from the per-SoC ->init
> callbacks
>
> drivers/thermal/qcom/tsens-v0_1.c | 9 +++++----
> drivers/thermal/qcom/tsens-v1.c | 7 ++++---
> drivers/thermal/qcom/tsens-v2.c | 2 +-
> drivers/thermal/qcom/tsens.c | 2 +-
> 4 files changed, 11 insertions(+), 9 deletions(-)
>
>
> base-commit: 2dc1f296b5754dd2441fc8b6613a362a47f6b98f
prev parent reply other threads:[~2026-11-04 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 14:57 Christian Schmidbauer
2026-11-04 14:57 ` [PATCH 1/2] thermal/drivers/qcom/tsens: Drop __init from init_common() Christian Schmidbauer
2026-11-04 14:57 ` [PATCH 2/2] thermal/drivers/qcom/tsens: Drop __init from the per-SoC ->init callbacks Christian Schmidbauer
2026-11-04 15:33 ` Daniel Lezcano [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=98d01186-7d87-459e-8c18-db201baef34a@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=amitk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=lumag@kernel.org \
--cc=opensource@grische.xyz \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@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
all inboxes | Powered by JetHome®