From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
bpf <bpf@vger.kernel.org>,
dwarves@vger.kernel.org,
Kumar Kartikeya Dwivedi <memxor@gmail.com>
Subject: Re: pahole and gcc-14 issues
Date: Tue, 29 Apr 2025 12:29:57 -0700 [thread overview]
Message-ID: <m2ldrihikq.fsf@gmail.com> (raw)
In-Reply-To: <CAEf4BzZgQMV+Gtiob_K-uuizyuqajyLjnGbKOJLyiGB=DxmY2Q@mail.gmail.com> (Andrii Nakryiko's message of "Tue, 29 Apr 2025 08:37:07 -0700")
Andrii Nakryiko <andrii.nakryiko@gmail.com> writes:
[...]
> Ok, so sleeping on this a bit more, I'm hesitant to do this more
> generic approach, as now we'll be running a risk of potentially
> looping indefinitely (the max_depth check I added doesn't completely
> prevent this).
Is that different from what happens already?
/* Check if given two types are identical STRUCT/UNION definitions */
static bool btf_dedup_identical_structs(struct btf_dedup *d, __u32 id1, __u32 id2)
{
[...]
for (i = 0, n = btf_vlen(t1); i < n; i++, m1++, m2++) {
if (...
!btf_dedup_identical_structs(d, m1->type, m2->type)) // <-- recursion,
return false; // afaiu it is unbounded.
}
return true;
}
E.g. adding an array to mark visited types and stop descend should stop
inifinite recurusion. I agree with Alan, the patch you shared in the
evening looks interesting. (But it was butchered by gmail,
fixing patches by hand is a bit annoyiong, maybe just attach such files?).
[...]
next prev parent reply other threads:[~2025-04-29 19:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 14:50 pahole and gcc-14 issues Alexei Starovoitov
2025-04-25 17:50 ` Alan Maguire
2025-04-25 17:58 ` Andrii Nakryiko
2025-04-25 20:36 ` Alan Maguire
2025-04-25 20:41 ` Andrii Nakryiko
2025-04-26 17:28 ` Alan Maguire
2025-04-28 15:21 ` Alan Maguire
2025-04-28 19:36 ` Arnaldo Carvalho de Melo
2025-04-28 19:50 ` Arnaldo Carvalho de Melo
2025-04-28 22:12 ` Alexei Starovoitov
2025-04-29 0:33 ` Andrii Nakryiko
2025-04-29 6:59 ` Andrii Nakryiko
2025-04-29 15:37 ` Andrii Nakryiko
2025-04-29 15:55 ` Alan Maguire
2025-04-29 19:29 ` Eduard Zingerman [this message]
2025-04-29 19:50 ` Andrii Nakryiko
2025-04-29 20:34 ` Eduard Zingerman
2025-04-29 20:55 ` Alexei Starovoitov
2025-04-29 21:44 ` Andrii Nakryiko
2025-04-25 20:58 ` Andrii Nakryiko
2025-04-25 18:14 ` Eduard Zingerman
2025-04-25 19:43 ` Eduard Zingerman
2025-04-25 20:16 ` Alexei Starovoitov
2025-04-25 20:25 ` Eduard Zingerman
2025-04-25 20:30 ` Alexei Starovoitov
2025-04-25 20:30 ` Eduard Zingerman
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=m2ldrihikq.fsf@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=memxor@gmail.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 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.