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>,
Martin KaFai Lau <martin.lau@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
kkd@meta.com, kernel-team@meta.com
Subject: [PATCH bpf v1 0/2] Fix bpf_throw() <> global subprogs interaction
Date: Sat, 16 May 2026 04:24:23 +0200 [thread overview]
Message-ID: <20260516022426.2109698-1-memxor@gmail.com> (raw)
There is a bug where bpf_throw()'s reachability across global subprogs
is missed by the verifier, leading to successful verification when any
kernel resource or lock is held across global subprog call boundary.
Fix this by effect summarization like other related side effects and
propagate exception reachability into callees.
Kumar Kartikeya Dwivedi (2):
bpf: Check global subprog exception paths
selftests/bpf: Cover global subprog exception leaks
include/linux/bpf_verifier.h | 2 ++
kernel/bpf/cfg.c | 13 ++++++++++-
kernel/bpf/verifier.c | 23 ++++++++++++++-----
.../selftests/bpf/progs/exceptions_fail.c | 22 ++++++++++++++++++
4 files changed, 53 insertions(+), 7 deletions(-)
base-commit: a828abbb897657451d96ad7bf20f1893ac983bb9
--
2.53.0
next reply other threads:[~2026-05-16 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 2:24 Kumar Kartikeya Dwivedi [this message]
2026-05-16 2:24 ` [PATCH bpf v1 1/2] bpf: Check global subprog exception paths Kumar Kartikeya Dwivedi
2026-05-16 2:24 ` [PATCH bpf v1 2/2] selftests/bpf: Cover global subprog exception leaks 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=20260516022426.2109698-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=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=martin.lau@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