From: Eduard Zingerman <eddyz87@gmail.com>
To: Paul Houssel <paulhoussel2@gmail.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Martin Horth <martin.horth@telecom-sudparis.eu>,
Ouail Derghal <ouail.derghal@imt-atlantique.fr>,
Guilhem Jazeron <guilhem.jazeron@inria.fr>,
Ludovic Paillat <ludovic.paillat@inria.fr>,
Robin Theveniaut <robin.theveniaut@irit.fr>,
Tristan d'Audibert <tristan.daudibert@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Paul Houssel <paul.houssel@orange.com>
Subject: Re: [PATCH v2 2/2] selftests/bpf: add BTF dedup tests for recursive typedef definitions
Date: Wed, 12 Nov 2025 12:28:41 -0800 [thread overview]
Message-ID: <a2578a0ee81f5e5bde327192b1544d5d1c9840fb.camel@gmail.com> (raw)
In-Reply-To: <c381ca44fccbde23fec1d67131c13fec162603d7.1762956565.git.paul.houssel@orange.com>
On Wed, 2025-11-12 at 15:11 +0100, Paul Houssel wrote:
Lgtm, one nit below:
> +{
> + .descr = "dedup: recursive typedef",
> + /*
> + * This test simulates a recursive typedef, which in GO is defined as such:
> + *
> + * type Foo func() Foo
> + *
> + * In BTF terms, this is represented as a TYPEDEF referencing
> + * a FUNC_PROTO that returns the same TYPEDEF.
> + */
> + .input = {
> + .raw_types = {
> + /*
> + * [1] typedef Foo -> func() Foo
> + * [2] func_proto() -> Foo
> + */
> + BTF_TYPEDEF_ENC(NAME_NTH(1), 2), /* [1] */
> + BTF_FUNC_PROTO_ENC(1, 0), /* [2] */
Nit:
Maybe repeat the above two types, just to make sure that deduplication happens?
> + BTF_END_RAW,
> + },
> + BTF_STR_SEC("\0Foo"),
> + },
> + .expect = {
> + .raw_types = {
> + BTF_TYPEDEF_ENC(NAME_NTH(1), 2), /* [1] */
> + BTF_FUNC_PROTO_ENC(1, 0), /* [2] */
> + BTF_END_RAW,
> + },
> + BTF_STR_SEC("\0Foo"),
> + },
> +},
[...]
prev parent reply other threads:[~2025-11-12 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 14:11 [PATCH v2 0/2] libbpf: fix BTF dedup to support recursive typedef Paul Houssel
2025-11-12 14:11 ` [PATCH v2 1/2] libbpf: fix BTF dedup to support recursive typedef definitions Paul Houssel
2025-11-12 20:16 ` Eduard Zingerman
2025-11-12 14:11 ` [PATCH v2 2/2] selftests/bpf: add BTF dedup tests for " Paul Houssel
2025-11-12 20:28 ` Eduard Zingerman [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=a2578a0ee81f5e5bde327192b1544d5d1c9840fb.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=guilhem.jazeron@inria.fr \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ludovic.paillat@inria.fr \
--cc=martin.horth@telecom-sudparis.eu \
--cc=martin.lau@linux.dev \
--cc=ouail.derghal@imt-atlantique.fr \
--cc=paul.houssel@orange.com \
--cc=paulhoussel2@gmail.com \
--cc=robin.theveniaut@irit.fr \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tristan.daudibert@gmail.com \
--cc=yonghong.song@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