From: Quentin Monnet <qmo@kernel.org>
To: Maxim Skokov <skokovmaksimevg@gmail.com>, bpf@vger.kernel.org
Cc: 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 1/3] bpftool: Print ENOTSUPP as "Operation not supported"
Date: Fri, 16 Oct 2026 21:08:21 +0100 [thread overview]
Message-ID: <bcab1d31-7103-4f29-9078-8683c3d4e3ae@kernel.org> (raw)
In-Reply-To: <20261016194825.230433-2-skokovmaksimevg@gmail.com>
2026-10-16 22:47 UTC+0300 ~ Maxim Skokov <skokovmaksimevg@gmail.com>
> Some BPF commands return ENOTSUPP (524) to user space: iterating local
> storage maps, element operations on ringbuf maps, creating an LRU hash
> map without preallocation, freezing a struct_ops map, or running a
> program type that has no test_run. ENOTSUPP is kernel internal, so
> strerror() only gives "Unknown error 524":
>
> # bpftool map getnext pinned /sys/fs/bpf/sk_storage
> Error: can't get next key: Unknown error 524
>
> Add a small helper that knows ENOTSUPP and use it where bpftool prints
> the error of map create, map element operations, map freeze and prog
> run.
>
> Suggested-by: Daniel Borkmann <daniel@iogearbox.net>
> Assisted-by: LLM
> Signed-off-by: Maxim Skokov <skokovmaksimevg@gmail.com>
Acked-by: Quentin Monnet <qmo@kernel.org>
Thank you
next prev parent reply other threads:[~2026-10-16 20:08 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 [this message]
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 ` [PATCH bpf-next v5 0/3] bpftool: Fail map dump for " patchwork-bot+netdevbpf
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=bcab1d31-7103-4f29-9078-8683c3d4e3ae@kernel.org \
--to=qmo@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=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