Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Tianyi Chen <hi@tychen.cc>
To: 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, ast@kernel.org,
	hi@tychen.cc
Subject: [PATCH bpf-next v10 0/4] bpftool: Add recursive map dumping
Date: Wed, 04 Nov 2026 04:01:23 +0900	[thread overview]
Message-ID: <cover.1793732336.git.hi@tychen.cc> (raw)

Rebased on current bpf-next, including Maxim's merged map-dump fixes.
The map-info fix and its tests are separate patches 1-2, included here
so mixed-BTF dumps also work on kernels without the kernel-side fix.

Changes in v10:
- Split the generic info resets from the recursive implementation.
- Rename the recursive test to avoid the upstream test-file collision.
- Preserve Quentin's Fixes/Acked-by tags and update the ENOTSUPP checks
  for the merged error-message formatter.

All 21 focused subtests pass on x86-64 KVM with Linux 7.2.13 and 7.3.0.
The four map-info regressions fail before the fix and pass after it.
All 33 subtests also pass when combined with the batch-dump series.

v9: https://lore.kernel.org/r/20260926014208.24773-1-hi@tychen.cc
Map-info v1: https://lore.kernel.org/r/cover.1790615923.git.hi@tychen.cc

Tianyi Chen (4):
  bpftool: Reset map info before each query in show and dump loops
  selftests/bpf: Check bpftool map info across mixed BTF maps
  bpftool: Add recursive map dumping
  selftests/bpf: Cover recursive bpftool map dumps

 .../bpf/bpftool/Documentation/bpftool-map.rst |  12 +-
 tools/bpf/bpftool/bash-completion/bpftool     |   3 +
 tools/bpf/bpftool/map.c                       | 154 ++++-
 .../prog_tests/bpftool_map_dump_recursive.c   | 605 ++++++++++++++++++
 .../bpf/prog_tests/bpftool_map_info.c         | 127 ++++
 5 files changed, 888 insertions(+), 13 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/prog_tests/bpftool_map_dump_recursive.c
 create mode 100644 tools/testing/selftests/bpf/prog_tests/bpftool_map_info.c


base-commit: cd5bc55288d4fd999595c8f2af6a5408cbe92a52
-- 
2.56.0


             reply	other threads:[~2026-11-03 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 19:01 Tianyi Chen [this message]
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
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=cover.1793732336.git.hi@tychen.cc \
    --to=hi@tychen.cc \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox