From: sashiko-bot@kernel.org
To: "Matt Fleming" <matt@readmodwrite.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Marco Elver" <elver@google.com>
Cc: "Alexander Potapenko" <glider@google.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Oscar Salvador" <osalvador@suse.de>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Caleb Kan" <ckan@cloudflare.com>,
"Caleb Kan" <calebkan1106@gmail.com>,
linux-mm@kvack.org, kasan-dev@googlegroups.com,
kernel-team@cloudflare.com,
"Matt Fleming" <mfleming@cloudflare.com>
Subject: Re: [PATCH v3 10/10] scripts/gdb: Decode compressed stack depot frames
Date: Sat, 14 Nov 2026 18:58:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-214931@kernel.org> (raw)
In-Reply-To: <20261113185702.1332171-11-matt@readmodwrite.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] scripts/gdb: stack_record_entry() reads _text contents instead
of its address
--
commit 9494b015f36a201275730fea0979762f1a250f80
Author: Matt Fleming <mfleming@cloudflare.com>
scripts/gdb: Decode compressed stack depot frames
This commit exports STACK_RECORD_COMPRESSED to the GDB scripts and decodes
compressed stack depot frames on x86-64 and arm64 in stack_depot_fetch().
> diff --git a/scripts/gdb/linux/stackdepot.py b/scripts/gdb/linux/stackdepot.py
> index aaa18af25cd12..f689cacb3cb70 100644
> --- a/scripts/gdb/linux/stackdepot.py
> +++ b/scripts/gdb/linux/stackdepot.py
> @@ -20,6 +20,21 @@ def help():
> gdb.write("Unrecognized command\n")
> raise gdb.GdbError(t)
>
> +def stack_record_entry(stack, i):
> + if not int(stack['flags']) & constants.LX_STACK_RECORD_COMPRESSED:
> + return int(stack['entries'][i])
> +
> + # Mirror arch_stack_depot_frame_decompress().
> + payload = int(stack['compressed_entries'][i])
> + if utils.is_target_arch("x86-64"):
> + return 0xffffffff00000000 | payload
> + if utils.is_target_arch("aarch64"):
> + text = int(gdb.parse_and_eval("(unsigned long)_text"))
[Severity: Low]
Does gdb.parse_and_eval("(unsigned long)_text") read the memory contents at
_text instead of taking its address?
Unlike in C where char _text[] decays to a pointer, _text is defined only in
the linker script as an untyped ELF symbol, so casting it without & in GDB
reads the first 8 bytes at .head.text and produces bogus decompressed frame
addresses on arm64. Using (unsigned long)&_text, as in
scripts/gdb/linux/mm.py, evaluates to the symbol's address.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113185702.1332171-1-matt@readmodwrite.com?part=10
prev parent reply other threads:[~2026-11-14 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 18:56 [PATCH v3 00/10] stackdepot: store compressed frames in stack records Matt Fleming
2026-11-13 18:56 ` [PATCH v3 01/10] stackdepot: add caller-owned stack trace fetching Matt Fleming
2026-11-13 18:56 ` [PATCH v3 02/10] mm/kmemleak: use stack_depot_fetch_into() for leak reports Matt Fleming
2026-11-13 18:56 ` [PATCH v3 03/10] kmsan: use stack_depot_fetch_into() for origin reports Matt Fleming
2026-11-13 18:56 ` [PATCH v3 04/10] mm/slub: use stack_depot_fetch_into() for owner tracking Matt Fleming
2026-11-13 18:56 ` [PATCH v3 05/10] drm/locking: print deadlock backtraces with stack_depot_snprint() Matt Fleming
2026-11-13 18:56 ` [PATCH v3 06/10] mm/page_owner: Read stack traces with stack_depot_fetch_into() Matt Fleming
2026-11-13 18:56 ` [PATCH v3 07/10] stackdepot: Remove stack_depot_fetch() Matt Fleming
2026-11-13 18:57 ` [PATCH v3 08/10] stackdepot: add architecture hooks for compact frame storage Matt Fleming
2026-11-14 18:58 ` sashiko-bot
2026-11-13 18:57 ` [PATCH v3 09/10] stackdepot: Store compressed frames in stack records Matt Fleming
2026-11-14 18:58 ` sashiko-bot
2026-11-13 18:57 ` [PATCH v3 10/10] scripts/gdb: Decode compressed stack depot frames Matt Fleming
2026-11-14 18:58 ` 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=sashiko-outbox-214931@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=calebkan1106@gmail.com \
--cc=ckan@cloudflare.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-mm@kvack.org \
--cc=matt@readmodwrite.com \
--cc=mfleming@cloudflare.com \
--cc=osalvador@suse.de \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vbabka@kernel.org \
/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