From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, daniel@iogearbox.net,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf v2 00/11] skb/arena bugfixes
Date: Tue, 22 Sep 2026 19:40:19 +0000 [thread overview]
Message-ID: <179010601914.57201.17168926914102740622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922172028.6269-1-emil@etsalapatis.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 22 Sep 2026 17:20:17 +0000 you wrote:
> Set of verifier-focused bugfixes related to dynptrs, SKB
> management in BPF, and dynptrs.
>
> Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
>
> v1 -> v2 (https://lore.kernel.org/bpf/20260916050830.8774-1-emil@etsalapatis.com/)
>
> [...]
Here is the summary with links:
- [bpf,v2,01/11] bpf: Fix bounds check for skb-backed dynptrs
https://git.kernel.org/bpf/bpf/c/ed6eec97b534
- [bpf,v2,02/11] selftests/bpf: Test dynptr slices past end of skb
https://git.kernel.org/bpf/bpf/c/4fd72eb9f1c9
- [bpf,v2,03/11] bpf: Fix bpf_sock context code generation
https://git.kernel.org/bpf/bpf/c/4a4852376e3a
- [bpf,v2,04/11] selftests/bpf: Add selftests for rx_queue_mapping context access
https://git.kernel.org/bpf/bpf/c/dec0c209a680
- [bpf,v2,05/11] bpf: Reject pkt arguments in mutating subprogs
https://git.kernel.org/bpf/bpf/c/a6c1edfbe240
- [bpf,v2,06/11] selftests/bpf: Test rejection of pkt args to mutating subprogs
https://git.kernel.org/bpf/bpf/c/1ed69a54d318
- [bpf,v2,07/11] bpf: Prevent variable arena/non-arena register contents
https://git.kernel.org/bpf/bpf/c/f85f5917aa2f
- [bpf,v2,08/11] selftests/bpf: Test for mixed arena/nonarena code paths
https://git.kernel.org/bpf/bpf/c/a9e86dd9de4f
- [bpf,v2,09/11] bpf: Track whether dynptr type is known
(no matching commit)
- [bpf,v2,10/11] bpf: Track skb memory invalidation by packet-backed dynptrs
(no matching commit)
- [bpf,v2,11/11] selftests/bpf: Test dynptr slice invalidation on skb clobber
(no matching commit)
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-22 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:20 [PATCH bpf v2 00/11] skb/arena bugfixes Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 01/11] bpf: Fix bounds check for skb-backed dynptrs Emil Tsalapatis
2026-09-22 17:27 ` sashiko-bot
2026-09-22 20:15 ` Amery Hung
2026-09-22 17:20 ` [PATCH bpf v2 02/11] selftests/bpf: Test dynptr slices past end of skb Emil Tsalapatis
2026-09-22 17:28 ` sashiko-bot
2026-09-22 20:16 ` Amery Hung
2026-09-22 17:20 ` [PATCH bpf v2 03/11] bpf: Fix bpf_sock context code generation Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 04/11] selftests/bpf: Add selftests for rx_queue_mapping context access Emil Tsalapatis
2026-09-22 17:36 ` sashiko-bot
2026-09-22 17:20 ` [PATCH bpf v2 05/11] bpf: Reject pkt arguments in mutating subprogs Emil Tsalapatis
2026-09-22 20:32 ` Amery Hung
2026-09-22 17:20 ` [PATCH bpf v2 06/11] selftests/bpf: Test rejection of pkt args to " Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 07/11] bpf: Prevent variable arena/non-arena register contents Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 08/11] selftests/bpf: Test for mixed arena/nonarena code paths Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 09/11] bpf: Track whether dynptr type is known Emil Tsalapatis
2026-09-22 18:46 ` Alexei Starovoitov
2026-09-22 20:23 ` Amery Hung
2026-09-22 20:28 ` Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 10/11] bpf: Track skb memory invalidation by packet-backed dynptrs Emil Tsalapatis
2026-09-22 20:06 ` Amery Hung
2026-09-22 20:29 ` Emil Tsalapatis
2026-09-22 17:20 ` [PATCH bpf v2 11/11] selftests/bpf: Test dynptr slice invalidation on skb clobber Emil Tsalapatis
2026-09-22 19: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=179010601914.57201.17168926914102740622.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=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
/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.