mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: ast@kernel.org, andrii@kernel.org, catalin.marinas@arm.com,
	daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
	ihor.solodrai@linux.dev, jolsa@kernel.org, memxor@gmail.com,
	mark.rutland@arm.com, martin.lau@linux.dev, puranjay@kernel.org,
	shuah@kernel.org, song@kernel.org, will@kernel.org,
	xukuohai@huaweicloud.com, yonghong.song@linux.dev,
	bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf v3 0/2] bpf, arm64: fix the exception callback's frame pointer
Date: Mon, 14 Sep 2026 05:00:06 +0000	[thread overview]
Message-ID: <178936200639.325205.5759223935386282492.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260907130624.611942-1-donggeunyoo.kernel@gmail.com>

Hello:

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

On Mon,  7 Sep 2026 22:06:22 +0900 you wrote:
> The arm64 JIT does not set BPF_REG_FP in the prologue of an exception
> callback, so the callback runs with whatever x25 held when bpf_throw()
> was called. A callback that materializes the register, for instance to
> pass the address of a local variable to a helper, then works on the
> frame of the subprogram that threw.
> 
> Patch 1 sets ctx->fp_used on that path, the same fix commit b114fcee766d
> ("bpf, arm64: Fix fp initialization for exception boundary") made for
> the exception boundary. Patch 2 adds a selftest that reaches the case.
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf, arm64: set up the frame pointer for the exception callback
    https://git.kernel.org/bpf/bpf/c/ef1fb82f1218
  - [bpf,v3,2/2] selftests/bpf: cover the exception callback using its own BPF stack
    https://git.kernel.org/bpf/bpf/c/26a43a5f8c31

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-09-14  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 13:06 Donggeun Yoo
2026-09-07 13:06 ` [PATCH bpf v3 1/2] bpf, arm64: set up the frame pointer for the exception callback Donggeun Yoo
2026-09-07 13:06 ` [PATCH bpf v3 2/2] selftests/bpf: cover the exception callback using its own BPF stack Donggeun Yoo
2026-09-07 13:43 ` [PATCH bpf v3 0/2] bpf, arm64: fix the exception callback's frame pointer Donggeun Yoo
2026-09-14  5:00 ` 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=178936200639.325205.5759223935386282492.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=donggeunyoo.kernel@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=shuah@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

all inboxes | Powered by JetHome®