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
Subject: Re: [PATCH v2 bpf 00/19] bpf: Remove BPF_F_ARENA_SCALAR, fix scalar evolution and scalar forks
Date: Wed, 28 Oct 2026 04:10:10 +0000 [thread overview]
Message-ID: <179316061083.488951.15898671743709955177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027190314.1440199-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 27 Oct 2026 19:02:55 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> This series removes BPF_F_ARENA_SCALAR and fixes bugs in scalar evolution,
> in maybe_fork_scalars() and in the trampoline of may_goto. The groups of
> patches do not depend on each other.
>
> v1 was Part 1 of "bpf: Stack in arena and a verifier that joins states"
> [1]. Parts 2 and 3 of that series are not here.
>
> [...]
Here is the summary with links:
- [v2,bpf,01/19] selftests/bpf: Remove tests for global data in arena
https://git.kernel.org/bpf/bpf/c/3c13b2e5a40e
- [v2,bpf,02/19] libbpf: Remove .arena.data
https://git.kernel.org/bpf/bpf/c/5b0678b2f9b9
- [v2,bpf,03/19] libbpf: Keep format strings of bpf_printk() in .rodata
https://git.kernel.org/bpf/bpf/c/58cbd31c399b
- [v2,bpf,04/19] selftests/bpf: Remove tests for arena access through numbers
https://git.kernel.org/bpf/bpf/c/fe8e06aa0575
- [v2,bpf,05/19] bpf: Remove BPF_F_ARENA_SCALAR
https://git.kernel.org/bpf/bpf/c/b62dee3a8bb5
- [v2,bpf,06/19] bpf, x86: Remove r0_on_stack from fetching atomics in arena
https://git.kernel.org/bpf/bpf/c/701edc66772b
- [v2,bpf,07/19] bpf: Clear delta of a register that scalar evolution widens
https://git.kernel.org/bpf/bpf/c/3f9924747c44
- [v2,bpf,08/19] selftests/bpf: Test that a widened register is not linked
https://git.kernel.org/bpf/bpf/c/165115760433
- [v2,bpf,09/19] selftests/bpf: Wait for the last maps of map_kptr to be freed
https://git.kernel.org/bpf/bpf/c/2ad395a38471
- [v2,bpf,10/19] selftests/bpf: Avoid a page fault in rcu_reentry while the handler is armed
https://git.kernel.org/bpf/bpf/c/3c0ca9f9a98e
- [v2,bpf,11/19] bpf: Don't widen a pointer to a buffer in scalar evolution
https://git.kernel.org/bpf/bpf/c/41750e5d682a
- [v2,bpf,12/19] selftests/bpf: Test a loop that moves a pointer to a buffer
https://git.kernel.org/bpf/bpf/c/1b4ed112beb8
- [v2,bpf,13/19] bpf: Don't clamp a register whose type changed in the loop
https://git.kernel.org/bpf/bpf/c/1536e9b4375f
- [v2,bpf,14/19] bpf: Reset the range of a packet pointer that scalar evolution clamps
https://git.kernel.org/bpf/bpf/c/41b06cfd1cea
- [v2,bpf,15/19] selftests/bpf: Test the clamp of pointers in scalar evolution
https://git.kernel.org/bpf/bpf/c/ed5036531482
- [v2,bpf,16/19] bpf: Finish the insn in the state that maybe_fork_scalars() splits off
https://git.kernel.org/bpf/bpf/c/19caa38daf9d
- [v2,bpf,17/19] selftests/bpf: Test maybe_fork_scalars() at the head of a counted loop
https://git.kernel.org/bpf/bpf/c/df9e4a87a8d3
- [v2,bpf,18/19] bpf: Keep stack arguments in arch_bpf_timed_may_goto()
https://git.kernel.org/bpf/bpf/c/4d0f560f4926
- [v2,bpf,19/19] selftests/bpf: Test stack arguments across may_goto
https://git.kernel.org/bpf/bpf/c/b433cdb1cc4f
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-28 4:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 19:02 [PATCH v2 bpf 00/19] bpf: Remove BPF_F_ARENA_SCALAR, fix scalar evolution and scalar forks Alexei Starovoitov
2026-10-27 19:02 ` [PATCH v2 bpf 01/19] selftests/bpf: Remove tests for global data in arena Alexei Starovoitov
2026-10-27 19:02 ` [PATCH v2 bpf 02/19] libbpf: Remove .arena.data Alexei Starovoitov
2026-10-27 19:02 ` [PATCH v2 bpf 03/19] libbpf: Keep format strings of bpf_printk() in .rodata Alexei Starovoitov
2026-10-27 19:02 ` [PATCH v2 bpf 04/19] selftests/bpf: Remove tests for arena access through numbers Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 05/19] bpf: Remove BPF_F_ARENA_SCALAR Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 06/19] bpf, x86: Remove r0_on_stack from fetching atomics in arena Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 07/19] bpf: Clear delta of a register that scalar evolution widens Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 08/19] selftests/bpf: Test that a widened register is not linked Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 09/19] selftests/bpf: Wait for the last maps of map_kptr to be freed Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 10/19] selftests/bpf: Avoid a page fault in rcu_reentry while the handler is armed Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 11/19] bpf: Don't widen a pointer to a buffer in scalar evolution Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 12/19] selftests/bpf: Test a loop that moves a pointer to a buffer Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 13/19] bpf: Don't clamp a register whose type changed in the loop Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 14/19] bpf: Reset the range of a packet pointer that scalar evolution clamps Alexei Starovoitov
2026-10-27 19:30 ` sashiko-bot
2026-10-27 20:09 ` Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 15/19] selftests/bpf: Test the clamp of pointers in scalar evolution Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 16/19] bpf: Finish the insn in the state that maybe_fork_scalars() splits off Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 17/19] selftests/bpf: Test maybe_fork_scalars() at the head of a counted loop Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 18/19] bpf: Keep stack arguments in arch_bpf_timed_may_goto() Alexei Starovoitov
2026-10-27 19:48 ` bot+bpf-ci
2026-10-28 4:53 ` Alexei Starovoitov
2026-10-27 19:03 ` [PATCH v2 bpf 19/19] selftests/bpf: Test stack arguments across may_goto Alexei Starovoitov
2026-10-28 4: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=179316061083.488951.15898671743709955177.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 \
/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