From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, bpf@vger.kernel.org, kpsingh@kernel.org
Subject: Re: [PATCH bpf-next 0/4] More gen_loader fixes #2
Date: Tue, 02 Jun 2026 16:50:11 +0000 [thread overview]
Message-ID: <178041901139.525612.7415193249618658369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602133052.423725-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 2 Jun 2026 15:30:48 +0200 you wrote:
> Another small follow-up from the sashiko findings about signed loaders.
> In particular, closing the gap to reject exclusive maps in iterators.
>
> Daniel Borkmann (4):
> bpf: Reject exclusive maps for bpf_map_elem iterators
> libbpf: Guard add_data() against size overflow
> selftests/bpf: Keep verifier_map_ptr exercising ops pointer access
> selftests/bpf: Test that exclusive maps are rejected as iter targets
>
> [...]
Here is the summary with links:
- [bpf-next,1/4] bpf: Reject exclusive maps for bpf_map_elem iterators
https://git.kernel.org/bpf/bpf-next/c/3c56ee343f94
- [bpf-next,2/4] libbpf: Guard add_data() against size overflow
https://git.kernel.org/bpf/bpf-next/c/7fef1796ec4d
- [bpf-next,3/4] selftests/bpf: Keep verifier_map_ptr exercising ops pointer access
https://git.kernel.org/bpf/bpf-next/c/082c41209771
- [bpf-next,4/4] selftests/bpf: Test that exclusive maps are rejected as iter targets
https://git.kernel.org/bpf/bpf-next/c/8dedd34122d0
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-06-02 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 13:30 [PATCH bpf-next 0/4] More gen_loader fixes #2 Daniel Borkmann
2026-06-02 13:30 ` [PATCH bpf-next 1/4] bpf: Reject exclusive maps for bpf_map_elem iterators Daniel Borkmann
2026-06-02 13:49 ` sashiko-bot
2026-06-02 15:38 ` Daniel Borkmann
2026-06-02 13:30 ` [PATCH bpf-next 2/4] libbpf: Guard add_data() against size overflow Daniel Borkmann
2026-06-02 13:30 ` [PATCH bpf-next 3/4] selftests/bpf: Keep verifier_map_ptr exercising ops pointer access Daniel Borkmann
2026-06-02 14:15 ` sashiko-bot
2026-06-02 13:30 ` [PATCH bpf-next 4/4] selftests/bpf: Test that exclusive maps are rejected as iter targets Daniel Borkmann
2026-06-02 16:50 ` 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=178041901139.525612.7415193249618658369.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@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.