BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, john.fastabend@gmail.com, memxor@gmail.com,
	yonghong.song@linux.dev
Subject: Re: [PATCH v4 0/5] libbpf: move arena variables out of the zero page
Date: Tue, 16 Dec 2025 19:00:13 +0000	[thread overview]
Message-ID: <176591161329.1242102.6732390197852635004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251216173325.98465-1-emil@etsalapatis.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue, 16 Dec 2025 12:33:20 -0500 you wrote:
> Modify libbpf to place arena globals at the end of 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.
> 
> [...]

Here is the summary with links:
  - [v4,1/5] selftests/bpf: explicitly account for globals in verifier_arena_large
    https://git.kernel.org/bpf/bpf-next/c/0355911ac021
  - [v4,2/5] bpf/verifier: do not limit maximum direct offset into arena map
    https://git.kernel.org/bpf/bpf-next/c/12a1fe6e12db
  - [v4,3/5] libbpf: turn relo_core->sym_off unsigned
    https://git.kernel.org/bpf/bpf-next/c/0aa721437e4b
  - [v4,4/5] libbpf: move arena globals to the end of the arena
    https://git.kernel.org/bpf/bpf-next/c/c1f61171d44b
  - [v4,5/5] selftests/bpf: add tests for the arena offset of globals
    https://git.kernel.org/bpf/bpf-next/c/19f12431b6c3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-12-16 19:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 17:33 [PATCH v4 0/5] libbpf: move arena variables out of the zero page Emil Tsalapatis
2025-12-16 17:33 ` [PATCH v4 1/5] selftests/bpf: explicitly account for globals in verifier_arena_large Emil Tsalapatis
2025-12-16 17:33 ` [PATCH v4 2/5] bpf/verifier: do not limit maximum direct offset into arena map Emil Tsalapatis
2025-12-16 18:02   ` bot+bpf-ci
2025-12-16 18:38     ` Andrii Nakryiko
2025-12-16 18:48       ` Eduard Zingerman
2025-12-16 23:32         ` Anton Protopopov
2025-12-16 17:33 ` [PATCH v4 3/5] libbpf: turn relo_core->sym_off unsigned Emil Tsalapatis
2025-12-16 17:33 ` [PATCH v4 4/5] libbpf: move arena globals to the end of the arena Emil Tsalapatis
2025-12-16 17:33 ` [PATCH v4 5/5] selftests/bpf: add tests for the arena offset of globals Emil Tsalapatis
2025-12-16 19:00 ` patchwork-bot+netdevbpf [this message]

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=176591161329.1242102.6732390197852635004.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=emil@etsalapatis.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