From: sashiko-bot@kernel.org
To: "Leo Yan" <leo.yan@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v10 8/9] perf cs-etm: Synthesize callchains for instruction samples
Date: Wed, 17 Jun 2026 21:35:10 +0000 [thread overview]
Message-ID: <20260617213510.9C2031F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260617-b4-arm_cs_callchain_support_v1-v10-8-e8b6e5d63db5@arm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The error path in `cs_etm__context()` destructively nullifies `tidq->frontend_thread`, leading to a predictable NULL pointer dereference crash in the perf tool when processing subsequent packets.
--
commit 3e6647ae053d9c4c2c79da5f0062f4a5c6da23e3
Author: Leo Yan <leo.yan@linux.dev>
perf cs-etm: Synthesize callchains for instruction samples
This patch adds callchain synthesis for instruction samples in CS ETM. It
allocates a callchain buffer and introduces cs_etm__context() to handle
context packets. The synthetic instruction events are updated to advertise
PERF_SAMPLE_CALLCHAIN.
> diff --git a/tools/perf/util/cs-etm.c b/tools/perf/util/cs-etm.c
> index 30536b919af73..67885ed43bab9 100644
> --- a/tools/perf/util/cs-etm.c
> +++ b/tools/perf/util/cs-etm.c
[ ... ]
> @@ -1910,6 +1947,34 @@ static int cs_etm__sample(struct cs_etm_queue *etmq,
> return 0;
> }
>
> +static int cs_etm__context(struct cs_etm_queue *etmq,
> + struct cs_etm_traceid_queue *tidq)
> +{
> + ocsd_ex_level el = tidq->packet->el;
> + struct machine *machine;
> + int ret;
> +
> + machine = cs_etm__get_machine(etmq, el);
> + if (!machine) {
> + ret = -EINVAL;
> + goto err;
> + }
> +
> + tidq->kernel_start = machine__kernel_start(machine);
> +
> + ret = cs_etm__etmq_update_thread(etmq, el, tidq->packet->tid,
> + &tidq->frontend_thread);
> + if (ret)
> + goto err;
> +
> + return 0;
> +
> +err:
> + thread__zput(tidq->frontend_thread);
[Severity: Medium]
Can this error path lead to a NULL pointer dereference crash in the perf tool?
If cs_etm__get_machine() fails, we take the err path and nullify
tidq->frontend_thread here.
If the caller, such as cs_etm__run_per_thread_timeless_decoder(), ignores
the error and continues processing the trace buffer, a subsequent
CS_ETM_RANGE packet will call cs_etm__synth_instruction_sample(). That function
unconditionally accesses the nullified pointer:
sample.pid = thread__pid(tidq->frontend_thread);
sample.tid = thread__tid(tidq->frontend_thread);
> + tidq->kernel_start = 0;
> + return ret;
> +}
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260617-b4-arm_cs_callchain_support_v1-v10-0-e8b6e5d63db5@arm.com?part=8
next prev parent reply other threads:[~2026-06-17 21:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 15:08 [PATCH v10 0/9] perf cs-etm: Support thread stack and callchain Leo Yan
2026-06-17 15:08 ` [PATCH v10 1/9] perf cs-etm: Fix thread leaks on trace queue init failure Leo Yan
2026-06-17 20:25 ` sashiko-bot
2026-06-17 15:08 ` [PATCH v10 2/9] perf cs-etm: Filter synthesized branch samples Leo Yan
2026-06-17 15:08 ` [PATCH v10 3/9] perf cs-etm: Decode ETE exception packets Leo Yan
2026-06-17 15:08 ` [PATCH v10 4/9] perf cs-etm: Refactor instruction size handling Leo Yan
2026-06-17 15:08 ` [PATCH v10 5/9] perf cs-etm: Use thread-stack for last branch entries Leo Yan
2026-06-17 20:56 ` sashiko-bot
2026-06-17 15:08 ` [PATCH v10 6/9] perf cs-etm: Flush thread stacks after decoder reset Leo Yan
2026-06-17 21:08 ` sashiko-bot
2026-06-17 15:08 ` [PATCH v10 7/9] perf cs-etm: Support call indentation Leo Yan
2026-06-17 21:20 ` sashiko-bot
2026-06-17 15:08 ` [PATCH v10 8/9] perf cs-etm: Synthesize callchains for instruction samples Leo Yan
2026-06-17 21:35 ` sashiko-bot [this message]
2026-06-17 15:09 ` [PATCH v10 9/9] perf test: Add Arm CoreSight callchain test Leo Yan
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=20260617213510.9C2031F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-perf-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.