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, eddyz87@gmail.com, martin.lau@kernel.org,
	memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v6 0/2] bpf: Relax 8 frame limitation for global subprogs
Date: Mon, 16 Mar 2026 18:30:08 +0000	[thread overview]
Message-ID: <177368580804.2824501.12875860174900759758.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260316161225.128011-1-emil@etsalapatis.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 16 Mar 2026 12:12:23 -0400 you wrote:
> The BPF verifier currently limits the maximum runtime call stack to
> 8 frames. Larger BPF programs like sched-ext schedulers routinely
> fail verification because they exceed this limit, even as they use
> very little actual stack space for each frame.
> 
> Relax the verifier to permit call stacks > 8 frames deep when the
> call stacks include global subprogs. The old 8 stack frame limit now
> only applies to call stacks composed entirely of static function calls.
> This works because global functions are each verified in isolation, so
> the verifier does not need to cross-reference verification state across
> the function call boundary, which has been the reason for limiting the
> call stack size in the first place.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/2] bpf: Only enforce 8 frame call stack limit for all-static stacks
    https://git.kernel.org/bpf/bpf-next/c/ad95d3c758d8
  - [bpf-next,v6,2/2] selftests/bpf: Add deep call stack selftests
    https://git.kernel.org/bpf/bpf-next/c/01d5d2f7d93d

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



      parent reply	other threads:[~2026-03-16 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 16:12 [PATCH bpf-next v6 0/2] bpf: Relax 8 frame limitation for global subprogs Emil Tsalapatis
2026-03-16 16:12 ` [PATCH bpf-next v6 1/2] bpf: Only enforce 8 frame call stack limit for all-static stacks Emil Tsalapatis
2026-03-16 17:01   ` bot+bpf-ci
2026-03-16 17:23     ` Emil Tsalapatis
2026-03-16 16:12 ` [PATCH bpf-next v6 2/2] selftests/bpf: Add deep call stack selftests Emil Tsalapatis
2026-03-16 18:30 ` 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=177368580804.2824501.12875860174900759758.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=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=song@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