From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next 0/5] bpf: Trampolines: the size of the image, the type of the return value
Date: Thu, 19 Nov 2026 05:10:06 +0000 [thread overview]
Message-ID: <179506500628.2857527.7428213974746565874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261119012909.3657417-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 19 Nov 2026 01:29:04 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Two things that the x86-64 and arm64 trampolines get wrong, and a limit
> that does not hold what it promises.
>
> Patches 1 - 3, the size of the image. BPF_MAX_TRAMP_LINKS programs are
> meant to fit in a page. They may not: on x86-64 with call depth tracking
> the pass that finds the size warns or writes past its scratch page. Let
> that pass count without an image, as the other JITs do. Then the size is
> the limit on each architecture, and BPF_MAX_TRAMP_LINKS can go.
>
> [...]
Here is the summary with links:
- [bpf-next,1/5] bpf, x86: Count the size of a trampoline, do not emit it
https://git.kernel.org/bpf/bpf-next/c/71531b583c94
- [bpf-next,2/5] selftests/bpf: Don't use BPF_MAX_TRAMP_LINKS
https://git.kernel.org/bpf/bpf-next/c/9e22f382de87
- [bpf-next,3/5] bpf: Remove BPF_MAX_TRAMP_LINKS
https://git.kernel.org/bpf/bpf-next/c/cfe2171b0bd9
- [bpf-next,4/5] bpf, x86, arm64: Fit the return value of a prog to the return type
https://git.kernel.org/bpf/bpf-next/c/664fde3a58f0
- [bpf-next,5/5] selftests/bpf: Test the width of the value of an fmod_ret program
https://git.kernel.org/bpf/bpf-next/c/7af0b756a8ef
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-11-19 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 1:29 [PATCH bpf-next 0/5] bpf: Trampolines: the size of the image, the type of the return value Alexei Starovoitov
2026-11-19 1:29 ` [PATCH bpf-next 1/5] bpf, x86: Count the size of a trampoline, do not emit it Alexei Starovoitov
2026-11-19 1:29 ` [PATCH bpf-next 2/5] selftests/bpf: Don't use BPF_MAX_TRAMP_LINKS Alexei Starovoitov
2026-11-19 1:29 ` [PATCH bpf-next 3/5] bpf: Remove BPF_MAX_TRAMP_LINKS Alexei Starovoitov
2026-11-19 1:39 ` sashiko-bot
2026-11-19 1:45 ` Alexei Starovoitov
2026-11-19 2:08 ` bot+bpf-ci
2026-11-19 1:29 ` [PATCH bpf-next 4/5] bpf, x86, arm64: Fit the return value of a prog to the return type Alexei Starovoitov
2026-11-19 1:29 ` [PATCH bpf-next 5/5] selftests/bpf: Test the width of the value of an fmod_ret program Alexei Starovoitov
2026-11-19 5: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=179506500628.2857527.7428213974746565874.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
/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