From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
Nicholas Carlini <npc@anthropic.com>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf v1 0/8] Misc bug fixes - part 5
Date: Sat, 5 Sep 2026 08:59:51 +0200 [thread overview]
Message-ID: <20260905070003.3193366-1-memxor@gmail.com> (raw)
A set of miscellaneous fixes for bugs reported by Nicholas. See commit
logs for details.
Kumar Kartikeya Dwivedi (8):
bpf: Make post-verification instruction rewrites killable
selftests/bpf: Test killing a loader during instruction rewrites
bpf: Preserve packet pointer class displacement in regsafe()
selftests/bpf: Test packet pointer class displacement pruning
bpf: Reject fall-through across subprogram boundaries
selftests/bpf: Test poisoned subprogram terminator
bpf: Assign lock identity to callback map values
selftests/bpf: Check callback map value lock identity
include/linux/bpf_verifier.h | 2 +
kernel/bpf/cfg.c | 21 +++
kernel/bpf/fixups.c | 21 ++-
kernel/bpf/states.c | 42 +++++-
kernel/bpf/verifier.c | 14 ++
.../selftests/bpf/prog_tests/core_reloc_raw.c | 113 +++++++++++++++
.../bpf/prog_tests/prog_load_signal.c | 131 ++++++++++++++++++
.../selftests/bpf/prog_tests/verifier.c | 2 +
.../bpf/progs/verifier_callback_lock.c | 73 ++++++++++
.../progs/verifier_xdp_direct_packet_access.c | 44 ++++++
10 files changed, 460 insertions(+), 3 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/prog_load_signal.c
create mode 100644 tools/testing/selftests/bpf/progs/verifier_callback_lock.c
base-commit: b75a000f2ac15f4778ddd6d9298d60b24ad776fa
--
2.53.0
next reply other threads:[~2026-09-05 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 6:59 Kumar Kartikeya Dwivedi [this message]
2026-09-05 6:59 ` [PATCH bpf v1 1/8] bpf: Make post-verification instruction rewrites killable Kumar Kartikeya Dwivedi
2026-09-05 8:02 ` bot+bpf-ci
2026-09-05 6:59 ` [PATCH bpf v1 2/8] selftests/bpf: Test killing a loader during instruction rewrites Kumar Kartikeya Dwivedi
2026-09-05 7:13 ` sashiko-bot
2026-09-05 7:15 ` Kumar Kartikeya Dwivedi
2026-09-05 8:02 ` bot+bpf-ci
2026-09-05 6:59 ` [PATCH bpf v1 3/8] bpf: Preserve packet pointer class displacement in regsafe() Kumar Kartikeya Dwivedi
2026-09-05 8:02 ` bot+bpf-ci
2026-09-05 6:59 ` [PATCH bpf v1 4/8] selftests/bpf: Test packet pointer class displacement pruning Kumar Kartikeya Dwivedi
2026-09-05 8:02 ` bot+bpf-ci
2026-09-05 6:59 ` [PATCH bpf v1 5/8] bpf: Reject fall-through across subprogram boundaries Kumar Kartikeya Dwivedi
2026-09-05 6:59 ` [PATCH bpf v1 6/8] selftests/bpf: Test poisoned subprogram terminator Kumar Kartikeya Dwivedi
2026-09-05 8:16 ` bot+bpf-ci
2026-09-05 6:59 ` [PATCH bpf v1 7/8] bpf: Assign lock identity to callback map values Kumar Kartikeya Dwivedi
2026-09-05 7:21 ` sashiko-bot
2026-09-05 7:32 ` Kumar Kartikeya Dwivedi
2026-09-05 6:59 ` [PATCH bpf v1 8/8] selftests/bpf: Check callback map value lock identity Kumar Kartikeya Dwivedi
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=20260905070003.3193366-1-memxor@gmail.com \
--to=memxor@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox