From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
npc@anthropic.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v7 00/10] Misc bug fixes - part 5
Date: Fri, 18 Sep 2026 01:10:05 +0000 [thread overview]
Message-ID: <178969380588.207424.12819902681607372321.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260917233222.2542500-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Eduard Zingerman <eddyz87@gmail.com>:
On Fri, 18 Sep 2026 01:32:08 +0200 you wrote:
> A set of miscellaneous fixes for bugs reported by Nicholas. See commit
> logs for details.
>
> Changelog:
> ----------
> v6 -> v7
> v6: https://lore.kernel.org/bpf/20260917111127.3780880-1-memxor@gmail.com
>
> [...]
Here is the summary with links:
- [bpf,v7,01/10] bpf: Make post-verification instruction rewrites killable
https://git.kernel.org/bpf/bpf/c/261b61d3735b
- [bpf,v7,02/10] bpf: Preserve packet pointer class displacement in regsafe()
https://git.kernel.org/bpf/bpf/c/fd16449a9b3b
- [bpf,v7,03/10] selftests/bpf: Test packet pointer class displacement pruning
https://git.kernel.org/bpf/bpf/c/2059d9af54f0
- [bpf,v7,04/10] bpf: Apply CO-RE relocations before subprogram validation
https://git.kernel.org/bpf/bpf/c/c26e97721b17
- [bpf,v7,05/10] selftests/bpf: Test early in-kernel CO-RE relocation
https://git.kernel.org/bpf/bpf/c/968ee7c06b62
- [bpf,v7,06/10] bpf: Restrict CO-RE poisoning to relocatable instructions
https://git.kernel.org/bpf/bpf/c/394ae398337c
- [bpf,v7,07/10] selftests/bpf: Test CO-RE instruction poisoning restrictions
https://git.kernel.org/bpf/bpf/c/3440505aca92
- [bpf,v7,08/10] bpf: Assign lock identity to callback map values
https://git.kernel.org/bpf/bpf/c/71919742c83c
- [bpf,v7,09/10] selftests/bpf: Check callback map value lock identity
https://git.kernel.org/bpf/bpf/c/04ae4ffc57a6
- [bpf,v7,10/10] libbpf: Reject truncated ldimm64 CO-RE relocations
https://git.kernel.org/bpf/bpf/c/b4e875d397da
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-18 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 23:32 [PATCH bpf v7 00/10] Misc bug fixes - part 5 Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 01/10] bpf: Make post-verification instruction rewrites killable Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 02/10] bpf: Preserve packet pointer class displacement in regsafe() Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 03/10] selftests/bpf: Test packet pointer class displacement pruning Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 04/10] bpf: Apply CO-RE relocations before subprogram validation Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 05/10] selftests/bpf: Test early in-kernel CO-RE relocation Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 06/10] bpf: Restrict CO-RE poisoning to relocatable instructions Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 07/10] selftests/bpf: Test CO-RE instruction poisoning restrictions Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 08/10] bpf: Assign lock identity to callback map values Kumar Kartikeya Dwivedi
2026-09-17 23:32 ` [PATCH bpf v7 09/10] selftests/bpf: Check callback map value lock identity Kumar Kartikeya Dwivedi
2026-09-17 23:46 ` sashiko-bot
2026-09-17 23:32 ` [PATCH bpf v7 10/10] libbpf: Reject truncated ldimm64 CO-RE relocations Kumar Kartikeya Dwivedi
2026-09-18 1:10 ` 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=178969380588.207424.12819902681607372321.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=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
--cc=npc@anthropic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.