From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, memxor@gmail.com, bpf@vger.kernel.org,
broonie@kernel.org
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Refactor cb_refs selftests
Date: Thu, 24 Sep 2026 01:50:05 +0000 [thread overview]
Message-ID: <179021460516.1272040.16158974939787437095.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923230717.3156345-1-ihor.solodrai@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 23 Sep 2026 16:07:17 -0700 you wrote:
> cb_refs matches verifier messages such as "Unreleased reference id=4
> alloc_insn=3". The ID is allocated from env->id_gen, so it changes
> whenever the verifier assigns another ID earlier in the program.
>
> In the bpf tree commit 71919742c83c ("bpf: Assign lock identity to
> callback map values") gives each callback map value an ID, and the
> nested_cb expectation was changed to id=5.
>
> [...]
Here is the summary with links:
- [bpf-next,v1] selftests/bpf: Refactor cb_refs selftests
https://git.kernel.org/bpf/bpf-next/c/11300f54bd88
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-09-24 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 23:07 [PATCH bpf-next v1] selftests/bpf: Refactor cb_refs selftests Ihor Solodrai
2026-09-23 23:18 ` Amery Hung
2026-09-24 0:26 ` Emil Tsalapatis
2026-09-24 1: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=179021460516.1272040.16158974939787437095.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=broonie@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=memxor@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