From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Tianyi Chen" <hi@tychen.cc>, <bpf@vger.kernel.org>
Cc: <qmo@kernel.org>, <andrii@kernel.org>, <eddyz87@gmail.com>,
<ihor.solodrai@linux.dev>, <linux-kselftest@vger.kernel.org>,
<skokovmaksimevg@gmail.com>, <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next v10 2/4] selftests/bpf: Check bpftool map info across mixed BTF maps
Date: Wed, 04 Nov 2026 02:27:14 +0000 [thread overview]
Message-ID: <DMM2KWGK3JH9.2TE6OINCZTTY@gmail.com> (raw)
In-Reply-To: <2c25cf3d118cce558cc58a207449b25c5f66b3a6.1793732336.git.hi@tychen.cc>
On Tue, Nov 03, 2026 at 11:01 AM Tianyi Chen <hi@tychen.cc> wrote:
> Create a typed map followed by a smaller untyped map with the same name.
> Check that full and named listings do not report BTF for the untyped map,
> JSON dumps match independently dumped contents, and plain dumps use raw
> output when the selected maps do not all have BTF.
This test cannot hit the bug from patch 1.
So the four subtests pass with and without patch 1.
pw-bot: cr
next prev parent reply other threads:[~2026-11-04 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 19:01 [PATCH bpf-next v10 0/4] bpftool: Add recursive map dumping Tianyi Chen
2026-11-03 19:01 ` [PATCH bpf-next v10 1/4] bpftool: Reset map info before each query in show and dump loops Tianyi Chen
2026-11-03 19:01 ` [PATCH bpf-next v10 2/4] selftests/bpf: Check bpftool map info across mixed BTF maps Tianyi Chen
2026-11-04 2:27 ` Alexei Starovoitov [this message]
2026-11-03 19:01 ` [PATCH bpf-next v10 3/4] bpftool: Add recursive map dumping Tianyi Chen
2026-11-04 2:28 ` Alexei Starovoitov
2026-11-03 19:01 ` [PATCH bpf-next v10 4/4] selftests/bpf: Cover recursive bpftool map dumps Tianyi Chen
2026-11-03 19:38 ` bot+bpf-ci
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=DMM2KWGK3JH9.2TE6OINCZTTY@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hi@tychen.cc \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=skokovmaksimevg@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.