From: sashiko-bot@kernel.org
To: "Aaron Tomlin" <atomlin@atomlin.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH perf-tools-next v6 1/5] perf trace: Fix error checking in btf_struct_scnprintf()
Date: Mon, 24 Aug 2026 13:40:20 +0000 [thread overview]
Message-ID: <20260824134021.222421F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260824133122.751733-2-atomlin@atomlin.com>
> btf_dump__dump_type_data() returns the positive number of bytes dumped on
> success, or a negative error code (e.g., -EINVAL) on failure.
>
> Currently, btf_struct_scnprintf() checks if btf_dump__dump_type_data()
> returns 0. When a negative error code is returned on failure, this check
> evaluates to false, causing the function to proceed down the success path
> and advance arg->augmented.args past the unprinted struct data before
> returning 0.
>
> Consequently, when syscall__scnprintf_args() falls back to the default
> argument beautifier upon receiving 0 from trace__btf_scnprintf(), the
> fallback beautifier or subsequent arguments read from an erroneously
> advanced augmented arguments buffer.
>
> Fix this by checking for '<= 0' ensuring that on any failure or 0-byte
> dump, 0 is returned without modifying the augmented arguments pointer.
>
> Fixes: cb32035214b9 ("perf trace: Pretty print augmented struct args using BTF")
> Reported-by: sashiko-bot <sashiko-bot@kernel.org>
> Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260824133122.751733-1-atomlin@atomlin.com?part=1
next prev parent reply other threads:[~2026-08-24 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:31 [PATCH perf-tools-next v6 0/5] perf trace: Symbolise kernel virtual addresses and function pointers Aaron Tomlin
2026-08-24 13:31 ` [PATCH perf-tools-next v6 1/5] perf trace: Fix error checking in btf_struct_scnprintf() Aaron Tomlin
2026-08-24 13:40 ` sashiko-bot [this message]
2026-09-04 21:17 ` Arnaldo Carvalho de Melo
2026-09-04 22:14 ` Aaron Tomlin
2026-08-24 13:31 ` [PATCH perf-tools-next v6 2/5] perf trace: Introduce kernel symbol beautifier for virtual addresses Aaron Tomlin
2026-08-24 13:38 ` sashiko-bot
2026-08-24 13:31 ` [PATCH perf-tools-next v6 3/5] perf trace: Auto-assign kernel symbol beautifier to function pointer fields Aaron Tomlin
2026-08-24 13:39 ` sashiko-bot
2026-08-24 13:31 ` [PATCH perf-tools-next v6 4/5] perf trace: Enhance BTF type formatting to symbolise kernel function pointers Aaron Tomlin
2026-08-24 13:49 ` sashiko-bot
2026-08-24 13:31 ` [PATCH perf-tools-next v6 5/5] perf tests: Add shell test for kernel symbol beautifier Aaron Tomlin
2026-08-24 13:38 ` sashiko-bot
2026-08-24 16:30 ` [PATCH perf-tools-next v6 0/5] perf trace: Symbolise kernel virtual addresses and function pointers Ian Rogers
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=20260824134021.222421F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=atomlin@atomlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox