From: sashiko-bot@kernel.org
To: "Jie Gan" <jie.gan@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: qcom: glymur: use Aggregator TNOC compatible
Date: Tue, 30 Jun 2026 11:31:38 +0000 [thread overview]
Message-ID: <20260630113139.A553C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630-fix-tracenoc-probe-issue-v3-5-7201e1841e94@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] System trace ID leak on device unbind or module removal for Aggregator TNOC platform devices because `tnoc_platform_remove` fails to free the allocated ID.
--
commit e1acaab1b46a7af95def9021d30728ac2de6b44a
Author: Jie Gan <jie.gan@oss.qualcomm.com>
arm64: dts: qcom: glymur: use Aggregator TNOC compatible
This commit updates the traceNoC node in the glymur device tree to use the
qcom,coresight-agtnoc compatible. This ensures the node probes as an
Aggregator TNOC and properly allocates a system trace ID.
> diff --git a/arch/arm64/boot/dts/qcom/glymur.dtsi b/arch/arm64/boot/dts/qcom/glymur.dtsi
> --- a/arch/arm64/boot/dts/qcom/glymur.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur.dtsi
> @@ -6038,12 +6038,12 @@ qm_tpdm_out: endpoint {
[ ... ]
> - itnoc@11200000 {
> - compatible = "qcom,coresight-itnoc";
> + tn@11200000 {
> + compatible = "qcom,coresight-agtnoc";
[Severity: High]
This is a pre-existing issue, but by switching this node to the
qcom,coresight-agtnoc compatible, does this expose a system trace ID leak on
device unbind?
When a platform device matching this compatible is bound, it allocates a
system trace ID. However, if the device is subsequently unbound via sysfs or
module unload, the current cleanup path fails to free the ID:
drivers/hwtracing/coresight/coresight-tnoc.c:tnoc_platform_remove() {
struct trace_noc_drvdata *drvdata = platform_get_drvdata(pdev);
coresight_unregister(drvdata->csdev);
pm_runtime_disable(&pdev->dev);
}
Unlike the AMBA counterpart trace_noc_remove(), this platform removal function
lacks a call to coresight_trace_id_put_system_id(drvdata->atid).
Since the global trace ID pool is strictly limited, could unbinding this newly
converted device repeatedly exhaust the system trace IDs and prevent further
CoreSight trace sessions from succeeding?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260630-fix-tracenoc-probe-issue-v3-0-7201e1841e94@oss.qualcomm.com?part=5
prev parent reply other threads:[~2026-06-30 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 10:36 [PATCH v3 0/5] Fix traceNoC probe issue on multiple QCOM platforms Jie Gan
2026-06-30 10:36 ` [PATCH v3 1/5] dt-bindings: arm: coresight-tnoc: Add standalone qcom,coresight-agtnoc compatible Jie Gan
2026-06-30 10:36 ` [PATCH v3 2/5] coresight: tnoc: Add AG tnoc standalone compatible to the platform driver Jie Gan
2026-06-30 10:57 ` sashiko-bot
2026-06-30 10:59 ` Jie Gan
2026-06-30 10:36 ` [PATCH v3 3/5] arm64: dts: qcom: kaanapali: fix traceNoC probe issue Jie Gan
2026-06-30 11:08 ` sashiko-bot
2026-06-30 12:53 ` Konrad Dybcio
2026-06-30 13:44 ` Jie Gan
2026-06-30 10:36 ` [PATCH v3 4/5] arm64: dts: qcom: sm8750: " Jie Gan
2026-06-30 11:19 ` sashiko-bot
2026-06-30 10:36 ` [PATCH v3 5/5] arm64: dts: qcom: glymur: use Aggregator TNOC compatible Jie Gan
2026-06-30 11:31 ` sashiko-bot [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=20260630113139.A553C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jie.gan@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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