From: Emil Tsalapatis <emil@etsalapatis.com>
To: bpf@vger.kernel.org
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, memxor@gmail.com,
yonghong.song@linux.dev, Emil Tsalapatis <emil@etsalapatis.com>
Subject: [PATCH v2 0/4] libbpf: move arena variables out of the zero
Date: Wed, 3 Dec 2025 11:26:21 -0500 [thread overview]
Message-ID: <20251203162625.13152-1-emil@etsalapatis.com> (raw)
Modify libbpf to place arena globals in a small offset inside the arena
mapping instead of the very beginning. This allows programs to leave
the "zero page" of the arena unmapped, so that NULL arena pointer
dereferences trigger a page fault and associated backtrace in BPF streams.
In contrast, the current policy of placing global data in the zero pages
means that NULL dereferences silently corrupt global data, e.g, arena
qspinlock state. This makes arena bugs more difficult to debug.
The patchset adds code to libbpf to move global arena data to the end of
the arena. At load time, libbpf adjusts each symbol's location within
the arena to point to the right location in the arena. The patchset
also adjusts the arena skeleton pointer to point to the arena globals,
now that they are not in the beginning of the arena region.
CHANGESET
=========
v1->v2: (https://lore.kernel.org/bpf/20251118030058.162967-1-emil@etsalapatis.com)
- Moved globals to the end of the mapping: (Andrii)
- Removed extra parameter for offset and parameter picking logic
- Removed padding in the skeleton
- Removed additional libbpf call
- Added Reviewed-by from Eduard on patch 1
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
Emil Tsalapatis (4):
selftests/bpf: explicitly account for globals in verifier_arena_large
bpf/verifier: do not limit maximum direct offset into arena map
libbpf: move arena globals to the end of the arena
selftests/bpf: add tests for the arena offset of globals
kernel/bpf/verifier.c | 8 +--
tools/lib/bpf/libbpf.c | 19 ++++--
.../selftests/bpf/prog_tests/verifier.c | 4 ++
.../bpf/progs/verifier_arena_globals1.c | 58 +++++++++++++++++++
.../bpf/progs/verifier_arena_globals2.c | 49 ++++++++++++++++
.../bpf/progs/verifier_arena_large.c | 21 +++++--
6 files changed, 147 insertions(+), 12 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/verifier_arena_globals1.c
create mode 100644 tools/testing/selftests/bpf/progs/verifier_arena_globals2.c
--
2.49.0
next reply other threads:[~2025-12-03 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 16:26 Emil Tsalapatis [this message]
2025-12-03 16:26 ` [PATCH v2 1/4] selftests/bpf: explicitly account for globals in verifier_arena_large Emil Tsalapatis
2025-12-03 16:26 ` [PATCH v2 2/4] bpf/verifier: do not limit maximum direct offset into arena map Emil Tsalapatis
2025-12-06 0:11 ` Andrii Nakryiko
2025-12-03 16:26 ` [PATCH v2 3/4] libbpf: move arena globals to the end of the arena Emil Tsalapatis
2025-12-03 16:52 ` bot+bpf-ci
2025-12-06 0:11 ` Andrii Nakryiko
2025-12-08 22:30 ` Emil Tsalapatis
2025-12-06 0:11 ` Andrii Nakryiko
2025-12-03 16:26 ` [PATCH v2 4/4] selftests/bpf: add tests for the arena offset of globals Emil Tsalapatis
2025-12-06 0:11 ` [PATCH v2 0/4] libbpf: move arena variables out of the zero Andrii Nakryiko
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=20251203162625.13152-1-emil@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--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