From: Eduard Zingerman <eddyz87@gmail.com>
To: Emil Tsalapatis <emil@etsalapatis.com>, bpf@vger.kernel.org
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, memxor@gmail.com, song@kernel.org,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v3 2/2] bpf: Add deep call stack selftests
Date: Tue, 03 Mar 2026 17:15:49 -0800 [thread overview]
Message-ID: <f7a9492407aafa4482addaa6a8879cc9441eecbd.camel@gmail.com> (raw)
In-Reply-To: <20260303043106.406099-3-emil@etsalapatis.com>
On Mon, 2026-03-02 at 23:31 -0500, Emil Tsalapatis wrote:
> Add tests that demonstrate the verifier support for deep call stacks
> while still enforcing maximum stack size limits.
>
> Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
[...]
> +/* Check we actually honor stack limits (33 * 16 = 528 > 512 = MAX_STACK_DEPTH). */
Nit: I was wondering why stack usage per func is 16, as each one only
consumes one slot. Turns out round_up_stack_depth() rounds things
up to 16. Could you please either add a comment here, or just add
a second long in each function?
> +SEC("syscall")
> +__failure __msg("combined stack size of 34 calls")
> +int global_func_deep_stack_fail(struct __sk_buff *skb)
> +{
> + return f32(123);
> +}
next prev parent reply other threads:[~2026-03-04 1:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 4:31 [PATCH bpf-next v3 0/2] bpf: Relax 8 frame limitation for global subprogs Emil Tsalapatis
2026-03-03 4:31 ` [PATCH bpf-next v3 1/2] bpf: Only enforce 8 frame call stack limit for all-static stacks Emil Tsalapatis
2026-03-03 5:13 ` bot+bpf-ci
2026-03-03 17:55 ` Emil Tsalapatis
2026-03-04 1:01 ` Eduard Zingerman
2026-03-05 19:38 ` Emil Tsalapatis
2026-03-05 20:46 ` Eduard Zingerman
2026-03-04 16:51 ` Mykyta Yatsenko
2026-03-05 17:36 ` Emil Tsalapatis
2026-03-03 4:31 ` [PATCH bpf-next v3 2/2] bpf: Add deep call stack selftests Emil Tsalapatis
2026-03-04 1:15 ` Eduard Zingerman [this message]
2026-03-05 17:37 ` Emil Tsalapatis
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=f7a9492407aafa4482addaa6a8879cc9441eecbd.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.