From: Eduard Zingerman <eddyz87@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org
Cc: daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, eddyz87@gmail.com, memxor@gmail.com
Subject: [PATCH bpf-next 0/2] bpf: remove artificial limitations on pointer types eligable for spilling
Date: Tue, 7 Jul 2026 17:44:27 -0700 [thread overview]
Message-ID: <20260707-missing-spillable-types-v1-0-44a92121dc41@gmail.com> (raw)
Track spills for the following register types precisely:
- PTR_TO_TP_BUFFER
- PTR_TO_INSN
- CONST_PTR_TO_DYNPTR
---
Eduard Zingerman (2):
bpf: remove artificial limitations on pointer types eligable for spilling
selftests/bpf: test cases for missing spill types
kernel/bpf/verifier.c | 39 +++++---------------
tools/testing/selftests/bpf/progs/verifier_gotox.c | 25 +++++++++++++
.../selftests/bpf/progs/verifier_spill_fill.c | 42 ++++++++++++++++++++++
3 files changed, 75 insertions(+), 31 deletions(-)
---
base-commit: 602701718649936eb287bf6c7ecf870ec54c6f71
change-id: 20260707-missing-spillable-types-4cd9350dc3d7
next reply other threads:[~2026-07-08 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 0:44 Eduard Zingerman [this message]
2026-07-08 0:44 ` [PATCH bpf-next 1/2] bpf: remove artificial limitations on pointer types eligable for spilling Eduard Zingerman
2026-07-08 1:31 ` bot+bpf-ci
2026-07-08 1:39 ` Kumar Kartikeya Dwivedi
2026-07-08 0:44 ` [PATCH bpf-next 2/2] selftests/bpf: test cases for missing spill types Eduard Zingerman
2026-07-08 1:40 ` [PATCH bpf-next 0/2] bpf: remove artificial limitations on pointer types eligable for spilling 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=20260707-missing-spillable-types-v1-0-44a92121dc41@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--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