From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, andrii@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf v2 1/4] bpf: Add cookie object to bpf maps
Date: Thu, 31 Jul 2025 19:04:28 +0000 [thread overview]
Message-ID: <175398866876.3245442.4453254948006628986.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250730234733.530041-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 31 Jul 2025 01:47:30 +0200 you wrote:
> Add a cookie to BPF maps to uniquely identify BPF maps for the timespan
> when the node is up. This is different to comparing a pointer or BPF map
> id which could get rolled over and reused.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---
> include/linux/bpf.h | 1 +
> kernel/bpf/syscall.c | 6 ++++++
> 2 files changed, 7 insertions(+)
Here is the summary with links:
- [bpf,v2,1/4] bpf: Add cookie object to bpf maps
https://git.kernel.org/bpf/bpf/c/12df58ad2942
- [bpf,v2,2/4] bpf: Move bpf map owner out of common struct
https://git.kernel.org/bpf/bpf/c/fd1c98f0ef5c
- [bpf,v2,3/4] bpf: Move cgroup iterator helpers to bpf.h
https://git.kernel.org/bpf/bpf/c/9621e60f59ea
- [bpf,v2,4/4] bpf: Fix oob access in cgroup local storage
https://git.kernel.org/bpf/bpf/c/abad3d0bad72
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:[~2025-07-31 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 23:47 [PATCH bpf v2 1/4] bpf: Add cookie object to bpf maps Daniel Borkmann
2025-07-30 23:47 ` [PATCH bpf v2 2/4] bpf: Move bpf map owner out of common struct Daniel Borkmann
2025-07-30 23:47 ` [PATCH bpf v2 3/4] bpf: Move cgroup iterator helpers to bpf.h Daniel Borkmann
2025-07-30 23:47 ` [PATCH bpf v2 4/4] bpf: Fix oob access in cgroup local storage Daniel Borkmann
2025-07-31 19:04 ` 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=175398866876.3245442.4453254948006628986.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 \
/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