From: Anton Protopopov <a.s.protopopov@gmail.com>
To: bpf@vger.kernel.org
Cc: Anton Protopopov <a.s.protopopov@gmail.com>
Subject: [PATCH bpf-next 0/2] A pair of follow ups for indirect jumps
Date: Fri, 28 Nov 2025 06:32:22 +0000 [thread overview]
Message-ID: <20251128063224.1305482-1-a.s.protopopov@gmail.com> (raw)
Two fixes suggested by Alexei in [1]. Resending as a series,
as the second patch depends on the first.
[1] https://lore.kernel.org/bpf/CAADnVQK3piReoo1ja=9hgz7aJ60Y_Jjur_JMOaYV8-Mn_VyE4A@mail.gmail.com/#R
Anton Protopopov (2):
bpf: force BPF_F_RDONLY_PROG on insn array creation
bpf: check for insn arrays in check_ptr_alignment
kernel/bpf/bpf_insn_array.c | 3 +++
kernel/bpf/verifier.c | 19 +++++++++----------
.../selftests/bpf/progs/verifier_gotox.c | 2 +-
3 files changed, 13 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2025-11-28 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 6:32 Anton Protopopov [this message]
2025-11-28 6:32 ` [PATCH bpf-next 1/2] bpf: force BPF_F_RDONLY_PROG on insn array creation Anton Protopopov
2025-11-28 6:32 ` [PATCH bpf-next 2/2] bpf: check for insn arrays in check_ptr_alignment Anton Protopopov
2025-11-28 23:20 ` [PATCH bpf-next 0/2] A pair of follow ups for indirect jumps 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=20251128063224.1305482-1-a.s.protopopov@gmail.com \
--to=a.s.protopopov@gmail.com \
--cc=bpf@vger.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