From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: bot+bpf-ci@kernel.org, qmo@kernel.org, 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, linux-kernel@vger.kernel.org,
martin.lau@kernel.org, clm@meta.com, ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v1] bpftool: Skip prog/map that disappears while looking it up by name
Date: Mon, 20 Jul 2026 16:40:24 +0800 [thread overview]
Message-ID: <e30b9522-bd38-41fd-93fa-3b8dcf01a3e2@linux.dev> (raw)
In-Reply-To: <4054b8846ea1b4cc0b2f5865891fd4add21499034aeb66adcd9e2fddf16cae83@mail.kernel.org>
On 7/20/26 4:02 PM, bot+bpf-ci@kernel.org wrote:
>> commit 084a91fc9c087ee9f5a2163da8368590cad6f121
>> Author: Jiayuan Chen <jiayuan.chen@linux.dev>
>>
>> bpftool: Skip prog/map that disappears while looking it up by name
>>
>> Looking up a prog or map by name walks the whole id space. There is a
>> window between bpf_prog_get_next_id()/bpf_map_get_next_id() and getting
>> an fd for that id in which an unrelated object can be freed, and the
>> lookup then fails with ENOENT and aborts the whole command.
>>
>> Skip such ids and keep walking, the same way do_show() already does.
>>
>> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
> This looks like a bug fix for the prog/map lookup functions. Should this
> include:
>
> Fixes: a479b8ce4ed1 ("tools/bpftool: Move map/prog parsing logic into common")
It's not worth backporting it.
People can always upgrade bpftool to latest version.
next prev parent reply other threads:[~2026-07-20 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 7:15 [PATCH bpf-next v1] bpftool: Skip prog/map that disappears while looking it up by name Jiayuan Chen
2026-07-20 8:02 ` bot+bpf-ci
2026-07-20 8:40 ` Jiayuan Chen [this message]
2026-07-20 15:10 ` 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=e30b9522-bd38-41fd-93fa-3b8dcf01a3e2@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--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