From: patchwork-bot+netdevbpf@kernel.org
To: Tianyi Chen <hi@tychen.cc>
Cc: bpf@vger.kernel.org, alexis.lothore@bootlin.com, qmo@kernel.org,
andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
ast@kernel.org, daniel@iogearbox.net, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf] selftests/bpf: Look up unpinned maps by ID in bpftool_maps_access
Date: Thu, 05 Nov 2026 16:40:05 +0000 [thread overview]
Message-ID: <179389680506.111114.10152549399816120190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104183323.409412-1-hi@tychen.cc>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 5 Nov 2026 03:33:23 +0900 you wrote:
> The unpinned subtests pass "name prot_map" or "name not_prot_map" to
> bpftool. Both maps are used by programs attached through trampolines,
> which are freed only after RCU grace periods and hold their map
> references until then. A run's maps therefore stay in the map ID table
> after its skeleton is destroyed, for about 300 ms in an x86-64 VM.
>
> If the test runs again within that window, the name matches maps from
> both runs, bpftool fails with "several maps match this handle", and
> the unpinned subtests fail.
>
> [...]
Here is the summary with links:
- [bpf] selftests/bpf: Look up unpinned maps by ID in bpftool_maps_access
https://git.kernel.org/bpf/bpf-next/c/325f263b2a7c
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-11-05 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:33 [PATCH bpf] selftests/bpf: Look up unpinned maps by ID in bpftool_maps_access Tianyi Chen
2026-11-05 9:54 ` Alexis Lothoré
2026-11-05 16:40 ` 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=179389680506.111114.10152549399816120190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@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=shuah@kernel.org \
/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