From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
xukuohai@huaweicloud.com, mark.rutland@arm.com, will@kernel.org,
catalin.marinas@arm.com
Subject: Re: [PATCH bpf-next v2 0/7] bpf, arm64: __arena kfunc and struct_ops arguments
Date: Fri, 14 Aug 2026 04:10:16 +0000 [thread overview]
Message-ID: <178668061664.3161817.18426400734023554692.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813190356.335181-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Thu, 13 Aug 2026 12:03:47 -0700 you wrote:
> The x86-64 JIT recently gained support for the __arena and
> __arena__nullable argument suffixes on kfuncs and struct_ops stubs. This
> adds the arm64 side and flips bpf_jit_supports_arena_args() on, so the
> verifier stops rejecting these programs on arm64.
>
> Patch 1 is an independent fix. save_args() reads stack-passed arguments
> at FP + 32, which only holds when the trampoline is entered through the
> fentry call and two frame records are pushed. A struct_ops trampoline is
> entered via blr and pushes one frame fewer, so its stack arguments start
> at FP + 16 and every one of them was read two slots off. No struct_ops
> member passed arguments on the stack until the test added by commit
> 2d4de9a493a0, which is why this went unnoticed. It carries a Fixes tag
> and can be taken separately; note that the test covering it only runs on
> arm64 once the rest of this series lands.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/7] bpf, arm64: Fix stack-passed arguments for indirect trampolines
https://git.kernel.org/bpf/bpf-next/c/50de1c47a41d
- [bpf-next,v2,2/7] arm64: insn: Add encoder for ADD/SUB (extended register)
https://git.kernel.org/bpf/bpf-next/c/f4adb983ef3d
- [bpf-next,v2,3/7] bpf, arm64: JIT __arena kfunc argument rebasing
https://git.kernel.org/bpf/bpf-next/c/760cb40cfd6a
- [bpf-next,v2,4/7] bpf, arm64: Convert struct_ops arena arguments in the trampoline
https://git.kernel.org/bpf/bpf-next/c/bb5bad6a78b6
- [bpf-next,v2,5/7] selftests/bpf: Add arm64 JIT-sequence tests for __arena kfunc arguments
https://git.kernel.org/bpf/bpf-next/c/1c5bc60f957d
- [bpf-next,v2,6/7] selftests/bpf: Enable __arena argument tests on arm64
https://git.kernel.org/bpf/bpf-next/c/05a3575f225c
- [bpf-next,v2,7/7] selftests/bpf: Test a multi-slot argument before a struct_ops arena argument
https://git.kernel.org/bpf/bpf-next/c/197d34b16943
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-08-14 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 19:03 [PATCH bpf-next v2 0/7] bpf, arm64: __arena kfunc and struct_ops arguments Puranjay Mohan
2026-08-13 19:03 ` [PATCH bpf-next v2 1/7] bpf, arm64: Fix stack-passed arguments for indirect trampolines Puranjay Mohan
2026-08-13 20:04 ` bot+bpf-ci
2026-08-13 19:03 ` [PATCH bpf-next v2 2/7] arm64: insn: Add encoder for ADD/SUB (extended register) Puranjay Mohan
2026-08-13 19:03 ` [PATCH bpf-next v2 3/7] bpf, arm64: JIT __arena kfunc argument rebasing Puranjay Mohan
2026-08-13 19:03 ` [PATCH bpf-next v2 4/7] bpf, arm64: Convert struct_ops arena arguments in the trampoline Puranjay Mohan
2026-08-14 3:50 ` Xu Kuohai
2026-08-13 19:03 ` [PATCH bpf-next v2 5/7] selftests/bpf: Add arm64 JIT-sequence tests for __arena kfunc arguments Puranjay Mohan
2026-08-13 19:03 ` [PATCH bpf-next v2 6/7] selftests/bpf: Enable __arena argument tests on arm64 Puranjay Mohan
2026-08-13 19:03 ` [PATCH bpf-next v2 7/7] selftests/bpf: Test a multi-slot argument before a struct_ops arena argument Puranjay Mohan
2026-08-14 4: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=178668061664.3161817.18426400734023554692.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=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=will@kernel.org \
--cc=xukuohai@huaweicloud.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