From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
tj@kernel.org, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v4 00/18] Raise BPF program stack size to 2KiB
Date: Thu, 24 Sep 2026 18:10:11 +0000 [thread overview]
Message-ID: <179027341165.1690644.15234244935000712349.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924165740.2146806-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 24 Sep 2026 18:57:01 +0200 you wrote:
> BPF programs get 512 bytes of stack. This series raises that to 2 KiB
> on x86-64 and arm64. The budget covers a whole call chain, or each frame
> on a private stack, and a single function may use all of it. The
> interpreter, offloaded programs and the other JITs keep 512 bytes.
>
> The x86-64 and arm64 JITs do not depend on 512-byte frames: both encode
> frame sizes in wide enough immediates, and on both a tail call pops the
> caller's frame and lands in the target's prologue before the target sets
> up its own.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/18] bpf: Add accessors for verifier stack slots
https://git.kernel.org/bpf/bpf-next/c/3b8da394c289
- [bpf-next,v4,02/18] bpf: Widen the stack slot index in the jump history
https://git.kernel.org/bpf/bpf-next/c/a9082d8a54c6
- [bpf-next,v4,03/18] bpf: Store linked registers in the jump history as an array
https://git.kernel.org/bpf/bpf-next/c/9eda94d7e898
- [bpf-next,v4,04/18] bpf: Track backtracking stack slots with bitmaps
https://git.kernel.org/bpf/bpf-next/c/765e7328d64d
- [bpf-next,v4,05/18] bpf: Track scratched stack slots with a bitmap
https://git.kernel.org/bpf/bpf-next/c/ec373f1f0788
- [bpf-next,v4,06/18] bpf: Treat unknown-size stack reads as reaching the frame top
https://git.kernel.org/bpf/bpf-next/c/1e054ab4aad6
- [bpf-next,v4,07/18] bpf: Size liveness stack masks by the stack each frame uses
https://git.kernel.org/bpf/bpf-next/c/481ceda77aeb
- [bpf-next,v4,08/18] bpf: Grow the verifier id scratch on demand
https://git.kernel.org/bpf/bpf-next/c/9f3d900a69be
- [bpf-next,v4,09/18] selftests/bpf: Cover the tail call caller stack depth limit
https://git.kernel.org/bpf/bpf-next/c/7fc140ba3dd9
- [bpf-next,v4,10/18] selftests/bpf: Check that narrow stack stores define no slot
https://git.kernel.org/bpf/bpf-next/c/76ab55b45244
- [bpf-next,v4,11/18] selftests/bpf: Check liveness merge of masks with different widths
https://git.kernel.org/bpf/bpf-next/c/10e9fa2b0b20
- [bpf-next,v4,12/18] bpf: Size the per-frame verifier structures for a 2 KiB stack
https://git.kernel.org/bpf/bpf-next/c/ecc441fc774e
- [bpf-next,v4,13/18] bpf: Bound program stack use by a per-program limit
https://git.kernel.org/bpf/bpf-next/c/9cfc28c9a8e6
- [bpf-next,v4,14/18] selftests/bpf: Add load conditions on the program stack limit
https://git.kernel.org/bpf/bpf-next/c/4fc52c1b549b
- [bpf-next,v4,15/18] selftests/bpf: Give the 512-byte stack boundary tests a 2 KiB twin
https://git.kernel.org/bpf/bpf-next/c/41fc2320aafe
- [bpf-next,v4,16/18] bpf, x86: Allow programs 2 KiB of stack
https://git.kernel.org/bpf/bpf-next/c/9f3bcf081ded
- [bpf-next,v4,17/18] bpf, arm64: Allow programs 2 KiB of stack
https://git.kernel.org/bpf/bpf-next/c/1d5306c11da2
- [bpf-next,v4,18/18] selftests/bpf: Test the 2 KiB stack budget
https://git.kernel.org/bpf/bpf-next/c/17d6fa978c00
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-24 18:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:57 [PATCH bpf-next v4 00/18] Raise BPF program stack size to 2KiB Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 01/18] bpf: Add accessors for verifier stack slots Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 02/18] bpf: Widen the stack slot index in the jump history Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 03/18] bpf: Store linked registers in the jump history as an array Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 04/18] bpf: Track backtracking stack slots with bitmaps Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 05/18] bpf: Track scratched stack slots with a bitmap Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 06/18] bpf: Treat unknown-size stack reads as reaching the frame top Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 07/18] bpf: Size liveness stack masks by the stack each frame uses Kumar Kartikeya Dwivedi
2026-09-24 17:52 ` bot+bpf-ci
2026-09-24 16:57 ` [PATCH bpf-next v4 08/18] bpf: Grow the verifier id scratch on demand Kumar Kartikeya Dwivedi
2026-09-24 17:38 ` bot+bpf-ci
2026-09-24 18:06 ` Alexei Starovoitov
2026-09-24 16:57 ` [PATCH bpf-next v4 09/18] selftests/bpf: Cover the tail call caller stack depth limit Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 10/18] selftests/bpf: Check that narrow stack stores define no slot Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 11/18] selftests/bpf: Check liveness merge of masks with different widths Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 12/18] bpf: Size the per-frame verifier structures for a 2 KiB stack Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 13/18] bpf: Bound program stack use by a per-program limit Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 14/18] selftests/bpf: Add load conditions on the program stack limit Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 15/18] selftests/bpf: Give the 512-byte stack boundary tests a 2 KiB twin Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 16/18] bpf, x86: Allow programs 2 KiB of stack Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 17/18] bpf, arm64: " Kumar Kartikeya Dwivedi
2026-09-24 16:57 ` [PATCH bpf-next v4 18/18] selftests/bpf: Test the 2 KiB stack budget Kumar Kartikeya Dwivedi
2026-09-24 18:10 ` 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=179027341165.1690644.15234244935000712349.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
--cc=tj@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