From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, xukuohai@huaweicloud.com,
catalin.marinas@arm.com, will@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/1] bpf, arm64: fix fp initialization for exception boundary
Date: Sat, 26 Jul 2025 19:30:10 +0000 [thread overview]
Message-ID: <175355821051.3674813.11697788265095490964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250722133410.54161-1-puranjay@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 22 Jul 2025 13:34:08 +0000 you wrote:
> In the ARM64 BPF JIT when prog->aux->exception_boundary is set for a BPF
> program, find_used_callee_regs() is not called because for a program acting
> as exception boundary, all callee saved registers are saved.
> find_used_callee_regs() sets `ctx->fp_used = true;` when it sees FP being
> used in any of the instructions.
> For programs acting as exception boundary, ctx->fp_used always remains
> false and therefore, BPF frame pointer is never set-up for such programs in
> the prologue.
>
> [...]
Here is the summary with links:
- [bpf-next,1/1] bpf, arm64: fix fp initialization for exception boundary
https://git.kernel.org/bpf/bpf-next/c/b114fcee766d
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:[~2025-07-26 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 13:34 [PATCH bpf-next 0/1] bpf, arm64: fix fp initialization for exception boundary Puranjay Mohan
2025-07-22 13:34 ` [PATCH bpf-next 1/1] " Puranjay Mohan
2025-07-23 7:46 ` Xu Kuohai
2025-07-26 19: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=175355821051.3674813.11697788265095490964.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--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