From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 0/2] Fix fastcall rewrite with indirect stack accesses
Date: Thu, 24 Sep 2026 16:40:05 +0000 [thread overview]
Message-ID: <179026800589.1646186.10786089414631608993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924075352.2343553-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 24 Sep 2026 09:53:48 +0200 you wrote:
> When a bpf_fastcall call is inlined, the verifier removes the spill/fill
> pairs around it and shrinks the stack frame to exclude their slots. Two
> kinds of stack access skip the check that must disable this rewrite, so
> the program can then access kernel stack outside its frame: stack
> buffers passed to helpers and kfuncs, which BPF CI reported after commit
> 5da4a9f26fca ("bpf: Preserve stack initialization for generic output
> buffers"), and a callee's load from its caller's stack, which checked
> the callee's frame instead of the caller's.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Check fastcall stack contract once for all stack accesses
https://git.kernel.org/bpf/bpf-next/c/ec3a69e7c021
- [bpf-next,v2,2/2] selftests/bpf: Test fastcall rewrite with indirect stack accesses
https://git.kernel.org/bpf/bpf-next/c/ba28c18f3439
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-24 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:53 [PATCH bpf-next v2 0/2] Fix fastcall rewrite with indirect stack accesses Kumar Kartikeya Dwivedi
2026-09-24 7:53 ` [PATCH bpf-next v2 1/2] bpf: Check fastcall stack contract once for all " Kumar Kartikeya Dwivedi
2026-09-24 7:53 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test fastcall rewrite with indirect " Kumar Kartikeya Dwivedi
2026-09-24 16:40 ` 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=179026800589.1646186.10786089414631608993.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=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
/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