From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight
Date: Mon, 26 May 2025 08:40:46 +0800 [thread overview]
Message-ID: <2f010e28-121e-4e60-bf48-5ee5bcd0cbea@oss.qualcomm.com> (raw)
In-Reply-To: <757925b7-3795-409a-9419-b33767c49e2e@oss.qualcomm.com>
On 5/22/2025 11:06 PM, Konrad Dybcio wrote:
> On 5/22/25 2:50 AM, Jie Gan wrote:
>> An infinite loop has been created by the Coresight devices. When only a
>> source device is enabled, the coresight_find_activated_sysfs_sink function
>> is recursively invoked in an attempt to locate an active sink device,
>> ultimately leading to a stack overflow and system crash. Therefore, disable
>> the replicator1 to break the infinite loop and prevent a potential stack
>> overflow.
>
> Is it something we can fix the driver not to do instead?
>
As Suzuki mentioned in other mail thread, it is very difficult to
observe the scenario that there is a loop in the path by current driver.
I tried fix the issue in driver before send this DT fix patch.
I will continue to seek an option of fixing in driver.
Thanks,
Jie
> Konrad
>
>>
>> replicator1_out -> funnel_swao_in6 -> tmc_etf_swao_in -> tmc_etf_swao_out
>> | |
>> replicator1_in replicator_swao_in
>> | |
>> replicator0_out1 replicator_swao_out0
>> | |
>> replicator0_in funnel_in1_in3
>> | |
>> tmc_etf_out <- tmc_etf_in <- funnel_merg_out <- funnel_merg_in1 <- funnel_in1_out
>>
>> [call trace]
>> dump_backtrace+0x9c/0x128
>> show_stack+0x20/0x38
>> dump_stack_lvl+0x48/0x60
>> dump_stack+0x18/0x28
>> panic+0x340/0x3b0
>> nmi_panic+0x94/0xa0
>> panic_bad_stack+0x114/0x138
>> handle_bad_stack+0x34/0xb8
>> __bad_stack+0x78/0x80
>> coresight_find_activated_sysfs_sink+0x28/0xa0 [coresight]
>> coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
>> coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
>> coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
>> coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
>> ...
>> coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
>> coresight_enable_sysfs+0x80/0x2a0 [coresight]
>>
>> side effect after the change:
>> Only trace data originating from AOSS can reach the ETF_SWAO and EUD sinks.
>>
>> Fixes: bf469630552a ("arm64: dts: qcom: qcs615: Add coresight nodes")
>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs615.dtsi | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs615.dtsi b/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> index f08ba09772f3..b67c1f8a1118 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/qcs615.dtsi
>> @@ -1902,6 +1902,7 @@ replicator@604a000 {
>>
>> clocks = <&aoss_qmp>;
>> clock-names = "apb_pclk";
>> + status = "disabled";
>>
>> in-ports {
>> port {
next prev parent reply other threads:[~2025-05-26 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 0:50 [PATCH] arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight Jie Gan
2025-05-22 15:06 ` Konrad Dybcio
2025-05-26 0:40 ` Jie Gan [this message]
2025-05-28 13:30 ` Mike Leach
2025-05-22 15:54 ` Suzuki K Poulose
2025-06-18 4:09 ` Bjorn Andersson
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=2f010e28-121e-4e60-bf48-5ee5bcd0cbea@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@linaro.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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