From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Zecheng Li <zli94@ncsu.edu>,
Yanbo Zhao <yzhao62@ncsu.edu>,
Tengda Wu <wutengda@huaweicloud.com>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH v2 2/4] perf dwarf-aux: Add die_has_flex_array() helper
Date: Sun, 13 Sep 2026 23:45:33 -0700 [thread overview]
Message-ID: <20260914064535.1671939-3-namhyung@kernel.org> (raw)
In-Reply-To: <20260914064535.1671939-1-namhyung@kernel.org>
The die_has_flex_array() returns true when the given type is a compound
type and contains an array at the end. To prevent an infinite recursion
add a depth field to the internal function.
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/perf/util/dwarf-aux.c | 77 +++++++++++++++++++++++++++++++++++++
tools/perf/util/dwarf-aux.h | 3 ++
2 files changed, 80 insertions(+)
diff --git a/tools/perf/util/dwarf-aux.c b/tools/perf/util/dwarf-aux.c
index d7160f87ac7d7ab3..465824e6513eb0ac 100644
--- a/tools/perf/util/dwarf-aux.c
+++ b/tools/perf/util/dwarf-aux.c
@@ -2180,3 +2180,80 @@ Dwarf_Die *die_deref_ptr_type(Dwarf_Die *ptr_die, int offset,
return die_get_member_type(&type_die, offset, die_mem);
}
+
+static bool is_flex_array_member(Dwarf_Die *mb_die)
+{
+ Dwarf_Die type_die;
+ Dwarf_Word size;
+
+ /* get the type of the member */
+ if (die_get_real_type(mb_die, &type_die) == NULL)
+ return false;
+
+ if (dwarf_tag(&type_die) != DW_TAG_array_type)
+ return false;
+
+ return dwarf_aggregate_size(&type_die, &size) < 0 || size == 0;
+}
+
+#define MAX_FLEX_ARRAY_RECURSION 256 /* arbitrary */
+
+static bool die_has_flex_array_recurse(Dwarf_Die *parent_die, int depth)
+{
+ Dwarf_Die die_mem, last_mb;
+ int tag = dwarf_tag(parent_die);
+
+ if (tag != DW_TAG_structure_type && tag != DW_TAG_union_type)
+ return false;
+
+ /* prevent infinite recursion */
+ if (depth > MAX_FLEX_ARRAY_RECURSION)
+ return false;
+
+ if (dwarf_child(parent_die, &die_mem))
+ return false;
+
+ do {
+ if (dwarf_tag(&die_mem) != DW_TAG_member)
+ continue;
+
+ if (tag == DW_TAG_union_type) {
+ if (is_flex_array_member(&die_mem))
+ return true;
+
+ if (die_get_real_type(&die_mem, &last_mb) &&
+ die_has_flex_array_recurse(&last_mb, depth + 1))
+ return true;
+ }
+
+ if (tag == DW_TAG_structure_type)
+ memcpy(&last_mb, &die_mem, sizeof(last_mb));
+
+ } while (dwarf_siblingof(&die_mem, &die_mem) == 0);
+
+ if (tag == DW_TAG_structure_type) {
+ if (is_flex_array_member(&last_mb))
+ return true;
+
+ if (die_get_real_type(&last_mb, &die_mem))
+ return die_has_flex_array_recurse(&die_mem, depth + 1);
+ }
+
+ return false;
+}
+
+/**
+ * die_has_flex_array - Check if the given type has a flex-array at the end
+ * @parent_die: a pointer to type DIE
+ *
+ * This function returns %true iff @parent_die is a struct type and has an
+ * array at the end. Note that the flex-array has no element, it should have
+ * no size and the parent size doesn't include the flex-array. So it should
+ * locate at the offset of the parent size.
+ *
+ * For simplicity, it assumes the parent size of aligned with the flex-array.
+ */
+bool die_has_flex_array(Dwarf_Die *parent_die)
+{
+ return die_has_flex_array_recurse(parent_die, 0);
+}
diff --git a/tools/perf/util/dwarf-aux.h b/tools/perf/util/dwarf-aux.h
index 161f0bf980b6ee6a..9b662db710220522 100644
--- a/tools/perf/util/dwarf-aux.h
+++ b/tools/perf/util/dwarf-aux.h
@@ -189,4 +189,7 @@ void die_collect_global_vars(Dwarf_Die *cu_die, struct die_var_type **var_types)
/* Get the frame base information from CFA */
int die_get_cfa(Dwarf *dwarf, u64 pc, int *preg, int *poffset);
+/* Check whether given type has a flex array */
+bool die_has_flex_array(Dwarf_Die *parent_die);
+
#endif /* _DWARF_AUX_H */
--
2.55.0.1032.g73a4cd73de-goog
next prev parent reply other threads:[~2026-09-14 6:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 6:45 [PATCH v2 0/4] perf annotate-data: Support flexible array types Namhyung Kim
2026-09-14 6:45 ` [PATCH v2 1/4] perf annotate-data: Convert type histogram to hashmap Namhyung Kim
2026-09-14 12:22 ` Tengda Wu
2026-09-14 18:56 ` Arnaldo Carvalho de Melo
2026-09-14 19:22 ` Arnaldo Carvalho de Melo
2026-09-14 20:42 ` Namhyung Kim
2026-09-14 6:45 ` Namhyung Kim [this message]
2026-09-14 12:14 ` [PATCH v2 2/4] perf dwarf-aux: Add die_has_flex_array() helper Tengda Wu
2026-09-14 20:28 ` Namhyung Kim
2026-09-14 6:45 ` [PATCH v2 3/4] perf annotate-date: Allow out-of-size access for flex-array types Namhyung Kim
2026-09-14 12:19 ` Tengda Wu
2026-09-14 20:39 ` Namhyung Kim
2026-09-14 6:45 ` [PATCH v2 4/4] perf annotate-data: Adjust type offset for flex-array Namhyung Kim
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=20260914064535.1671939-3-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--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=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=wutengda@huaweicloud.com \
--cc=xueshuai@linux.alibaba.com \
--cc=yzhao62@ncsu.edu \
--cc=zli94@ncsu.edu \
/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®