From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, memxor@gmail.com, npc@anthropic.com
Subject: Re: [PATCH bpf 1/2] bpf: don't rewrite bpf_fastcall patterns entered by a jump
Date: Fri, 04 Sep 2026 02:00:13 +0000 [thread overview]
Message-ID: <178848721364.4116251.5509582098405601051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903205820.1743087-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 3 Sep 2026 13:58:19 -0700 you wrote:
> mark_fastcall_pattern_for_call() must ensure that matched
> "spill; call; fill" instruction series is not interrupted by a jump.
> Otherwise the rewrite applied by bpf_remove_fastcall_spills_fills()
> is not sound.
>
> Record the instructions targeted by jumps in
> insn_aux_data[*].jump_target when the CFG is built and use this flag
> to stop growing a pattern at such an instruction. Jumps to the first
> spill are fine.
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: don't rewrite bpf_fastcall patterns entered by a jump
https://git.kernel.org/bpf/bpf/c/0b1c83dc3c44
- [bpf,2/2] selftests/bpf: bpf_fastcall patterns entered by a jump
https://git.kernel.org/bpf/bpf/c/65b1518c995c
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-09-04 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:58 [PATCH bpf 1/2] bpf: don't rewrite bpf_fastcall patterns entered by a jump Eduard Zingerman
2026-09-03 20:58 ` [PATCH bpf 2/2] selftests/bpf: " Eduard Zingerman
2026-09-04 2: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=178848721364.4116251.5509582098405601051.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=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=npc@anthropic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.