From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Skokov <skokovmaksimevg@gmail.com>
Cc: bpf@vger.kernel.org, qmo@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
ihor.solodrai@linux.dev, kuba@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, hi@tychen.cc
Subject: Re: [PATCH bpf-next v5 0/3] bpftool: Fail map dump for maps that can't be iterated
Date: Sat, 17 Oct 2026 14:50:05 +0000 [thread overview]
Message-ID: <179224860527.1268583.11977700163601405121.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016194825.230433-1-skokovmaksimevg@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 16 Oct 2026 22:47:55 +0300 you wrote:
> "bpftool map dump" treats only ENOENT from bpf_map_get_next_key() as the
> end of the map. Map types that can't be iterated (local storage, ringbuf,
> bloom filter, arena, queue, stack) fail on the first key, and bpftool
> prints an empty dump, "[]" or "Found 0 elements", with only a non-zero
> exit status.
>
> Patch 1 adds a helper that prints ENOTSUPP (524), which the kernel
> returns from some BPF commands, as "Operation not supported" instead of
> "Unknown error 524", and uses it for map create, map element
> operations, map freeze and prog run. Patch 2 asks for the first key
> before printing anything and fails with the map type and the error.
> Patch 3 adds a test_progs case on a socket storage map, and on a queue
> map without BTF for the plain output path.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] bpftool: Print ENOTSUPP as "Operation not supported"
https://git.kernel.org/bpf/bpf-next/c/b32b4956d451
- [bpf-next,v5,2/3] bpftool: Fail map dump for maps that can't be iterated
https://git.kernel.org/bpf/bpf-next/c/70ac4de43ad1
- [bpf-next,v5,3/3] selftests/bpf: Test bpftool map dump on maps that can't be iterated
https://git.kernel.org/bpf/bpf-next/c/631fee3f5a18
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-17 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 19:47 [PATCH bpf-next v5 0/3] bpftool: Fail map dump for maps that can't be iterated Maxim Skokov
2026-10-16 19:47 ` [PATCH bpf-next v5 1/3] bpftool: Print ENOTSUPP as "Operation not supported" Maxim Skokov
2026-10-16 20:08 ` Quentin Monnet
2026-10-16 19:47 ` [PATCH bpf-next v5 2/3] bpftool: Fail map dump for maps that can't be iterated Maxim Skokov
2026-10-16 19:47 ` [PATCH bpf-next v5 3/3] selftests/bpf: Test bpftool map dump on " Maxim Skokov
2026-10-16 20:08 ` qmo
2026-10-17 14:50 ` patchwork-bot+netdevbpf [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=179224860527.1268583.11977700163601405121.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=hi@tychen.cc \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--cc=shuah@kernel.org \
--cc=skokovmaksimevg@gmail.com \
--cc=song@kernel.org \
--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