From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 4/6] perf annotate-data: Bound the member nesting recursion
Date: Fri, 25 Sep 2026 08:39:21 -0700 [thread overview]
Message-ID: <araVqTiVF9DpkSmh@z2> (raw)
In-Reply-To: <20260925150657.1826942-5-acme@kernel.org>
On Fri, Sep 25, 2026 at 05:06:55PM +0200, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Members are added recursively, and a broken DIE can make a member's
> type point back at one of its own ancestors, recursing until the stack
> is gone; nothing usable comes out of nesting members 32 deep anyway, so
> stop there, marking the member as truncated and giving up on member
> types that don't resolve.
>
> The check is where the children of an aggregate would be expanded, so
> only struct/union members are marked as truncated.
>
> Assisted-by: LLM
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
> tools/perf/util/annotate-data.c | 20 ++++++++++++++++++--
> tools/perf/util/annotate-data.h | 3 +++
> 2 files changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/annotate-data.c b/tools/perf/util/annotate-data.c
> index bc9698abc6a9e055..19a6ecd67f28719d 100644
> --- a/tools/perf/util/annotate-data.c
> +++ b/tools/perf/util/annotate-data.c
> @@ -222,6 +222,12 @@ static bool data_type_less(struct rb_node *node_a, const struct rb_node *node_b)
> return strcmp(a->self.type_name, b->self.type_name) < 0;
> }
>
> +/*
> + * A broken type can point back at one of its own ancestors: bound the
> + * nesting so it doesn't recurse until the stack is gone.
> + */
> +#define MAX_MEMBER_DEPTH 32
> +
> /* Recursively add new members for struct/union */
> static int __add_member_cb(Dwarf_Die *die, void *arg)
> {
> @@ -236,6 +242,9 @@ static int __add_member_cb(Dwarf_Die *die, void *arg)
> if (dwarf_tag(die) != DW_TAG_member)
> return DIE_FIND_CB_SIBLING;
>
> + if (die_get_real_type(die, &die_mem) == NULL)
> + return DIE_FIND_CB_SIBLING;
> +
> member = zalloc(sizeof(*member));
> if (member == NULL)
> return DIE_FIND_CB_END;
> @@ -248,8 +257,6 @@ static int __add_member_cb(Dwarf_Die *die, void *arg)
> if (die_get_typename(die, &sb) < 0)
> strbuf_add(&sb, "(unknown type)", 14);
>
> - die_get_real_type(die, &die_mem);
> -
> if (dwarf_aggregate_size(&die_mem, &size) < 0 || size == 0) {
> if (dwarf_tag(&die_mem) == DW_TAG_array_type) { /* flex-array? */
> die_get_real_type(&die_mem, &die_mem);
> @@ -299,6 +306,7 @@ static int __add_member_cb(Dwarf_Die *die, void *arg)
> }
> member->size = size;
> member->offset = loc + parent->offset;
> + member->depth = parent->depth + 1;
> INIT_LIST_HEAD(&member->children);
>
> list_for_each_entry_reverse(prev, &parent->children, node) {
> @@ -313,6 +321,14 @@ static int __add_member_cb(Dwarf_Die *die, void *arg)
> member->is_union = true;
> /* fall through */
> case DW_TAG_structure_type:
> + /* Only aggregates have children to expand, so only they get truncated. */
> + if (member->depth >= MAX_MEMBER_DEPTH) {
> + /* Consumed by the JSON exporter added in a later series. */
> + member->truncated = true;
> + pr_debug_dtp("member nesting limit reached at %s\n",
> + member->type_name ?: "(unknown type)");
> + break;
> + }
> die_find_child(&die_mem, __add_member_cb, member, &die_mem);
> break;
> default:
> diff --git a/tools/perf/util/annotate-data.h b/tools/perf/util/annotate-data.h
> index 14b8113521a927cf..ca0abfb2a036d229 100644
> --- a/tools/perf/util/annotate-data.h
> +++ b/tools/perf/util/annotate-data.h
> @@ -61,6 +61,9 @@ struct annotated_member {
> int size;
> bool is_union;
> bool is_flex_array;
> + unsigned int depth;
> + /* Children not expanded because the nesting limit was reached */
> + bool truncated;
Nit: it'd be better to switch the order of the last two fields to reduce
the padding.
Thanks,
Namhyung
> };
>
> /**
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-09-25 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:06 [PATCH v5 0/6] perf annotate-data: Fix hangs on broken debug info, AMD mem record Arnaldo Carvalho de Melo
2026-09-25 15:06 ` [PATCH 1/6] perf dwarf-aux: Bound the type chases for broken debug info Arnaldo Carvalho de Melo
2026-09-25 15:18 ` Ian Rogers
2026-09-25 15:06 ` [PATCH 2/6] perf dwarf-aux: Add die_same_file() and die_get_type_die() Arnaldo Carvalho de Melo
2026-09-25 15:20 ` Ian Rogers
2026-09-25 15:06 ` [PATCH 3/6] perf annotate-data: Resolve type DIEs in the debug file they came from Arnaldo Carvalho de Melo
2026-09-25 15:35 ` Ian Rogers
2026-09-25 15:06 ` [PATCH 4/6] perf annotate-data: Bound the member nesting recursion Arnaldo Carvalho de Melo
2026-09-25 15:37 ` Ian Rogers
2026-09-25 15:39 ` Namhyung Kim [this message]
2026-09-25 15:43 ` Arnaldo Carvalho de Melo
2026-09-25 16:11 ` Arnaldo Carvalho de Melo
2026-09-25 15:06 ` [PATCH 5/6] perf mem record: Request PERF_SAMPLE_CPU by default Arnaldo Carvalho de Melo
2026-09-25 15:47 ` Ian Rogers
2026-09-25 15:06 ` [PATCH 6/6] perf mem record: Use the IBS swfilt filter when available Arnaldo Carvalho de Melo
2026-09-25 15:46 ` [PATCH v5 0/6] perf annotate-data: Fix hangs on broken debug info, AMD mem record Namhyung Kim
2026-09-25 15:48 ` Arnaldo Carvalho de Melo
2026-09-25 15:58 ` Arnaldo Carvalho de Melo
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=araVqTiVF9DpkSmh@z2 \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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
all inboxes | Powered by JetHome®