From: Taegu Ha <hataegu0826@gmail.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Yonghong Song <yonghong.song@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Shuah Khan <shuah@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, Taegu Ha <hataegu0826@gmail.com>
Subject: [PATCH v2 0/1] bpf: reject overlarge global subprog argument sizes
Date: Thu, 28 May 2026 14:25:32 +0900 [thread overview]
Message-ID: <20260528052533.3940181-1-hataegu0826@gmail.com> (raw)
In-Reply-To: <20260527052539.3388700-1-hataegu0826@gmail.com>
This rejects BTF-derived global subprog argument sizes that cannot be
represented by the verifier's signed access-size API.
The issue is not a large immediate in the generated BPF instruction stream.
The oversized BTF pointee size wraps the caller-side PTR_TO_STACK argument
check before the callee is verified with the original large mem_size.
Changes in v2:
- Expand the commit message to describe the caller/callee verifier mismatch.
- Keep the existing size expression unchanged after adding the S32_MAX guard,
as suggested by Yonghong.
Taegu Ha (1):
bpf: reject overlarge global subprog argument sizes
kernel/bpf/verifier.c | 5 +++++
.../bpf/progs/verifier_global_subprogs.c | 17 +++++++++++++++++
2 files changed, 22 insertions(+)
--
2.43.0
next prev parent reply other threads:[~2026-05-28 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 5:25 [PATCH bpf " Taegu Ha
2026-05-27 5:25 ` [PATCH bpf 1/1] " Taegu Ha
2026-05-27 16:59 ` Yonghong Song
2026-05-27 17:48 ` 하태구
2026-05-27 17:53 ` 하태구
2026-05-28 5:03 ` Yonghong Song
2026-05-28 5:25 ` Taegu Ha [this message]
2026-05-28 5:25 ` [PATCH v2 " Taegu Ha
2026-05-28 6:05 ` bot+bpf-ci
2026-05-28 6:21 ` [PATCH bpf-next v3] " Taegu Ha
2026-05-28 15:17 ` Yonghong Song
2026-06-01 1:00 ` patchwork-bot+netdevbpf
2026-06-01 6:04 ` 하태구
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=20260528052533.3940181-1-hataegu0826@gmail.com \
--to=hataegu0826@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®