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, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next 0/3] bpf: Fixes for unwind_goto and unwind_exit
Date: Wed, 21 Oct 2026 00:10:06 +0000 [thread overview]
Message-ID: <179254140628.280032.5891719215381607213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020231942.2568163-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 20 Oct 2026 23:19:38 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Two fixes for what the bots found in v4 [1] of the series that added
> unwind_goto and unwind_exit.
>
> Patch 1. unwind_exit of an exception callback is exit for the verifier, but
> JITs looked up the return address. The callback returns from the frame of
> the main prog. After freplace or a tail call that's a return to a prog, and
> the callback could end up in a pad that wasn't verified with it.
> It came with 'unwind_exit of an async or an exception callback is exit' in
> v4. For an async callback that's fine: it has a frame of its own.
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf: Make unwind_exit of an exception callback exit in JITs
https://git.kernel.org/bpf/bpf-next/c/6ff297f98b0c
- [bpf-next,2/3] bpf: Reject unwind_goto and unwind_exit in offloaded progs
https://git.kernel.org/bpf/bpf-next/c/9d1fbfc23675
- [bpf-next,3/3] selftests/bpf: Test unwind_exit of an exception callback
https://git.kernel.org/bpf/bpf-next/c/ad223de6d346
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-10-21 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 23:19 [PATCH bpf-next 0/3] bpf: Fixes for unwind_goto and unwind_exit Alexei Starovoitov
2026-10-20 23:19 ` [PATCH bpf-next 1/3] bpf: Make unwind_exit of an exception callback exit in JITs Alexei Starovoitov
2026-10-20 23:19 ` [PATCH bpf-next 2/3] bpf: Reject unwind_goto and unwind_exit in offloaded progs Alexei Starovoitov
2026-10-20 23:43 ` bot+bpf-ci
2026-10-21 0:08 ` Alexei Starovoitov
2026-10-21 2:23 ` Ihor Solodrai
2026-10-20 23:19 ` [PATCH bpf-next 3/3] selftests/bpf: Test unwind_exit of an exception callback Alexei Starovoitov
2026-10-21 0: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=179254140628.280032.5891719215381607213.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 \
--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