From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@kernel.org, void@manifault.com,
davemarchevsky@meta.com, tj@kernel.org, memxor@gmail.com,
netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v5 bpf-next 0/6] bpf: Introduce kptr RCU.
Date: Fri, 03 Mar 2023 16:50:20 +0000 [thread overview]
Message-ID: <167786222035.26859.4386915483809485037.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230303041446.3630-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 2 Mar 2023 20:14:40 -0800 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> v4->v5:
> fix typos, add acks.
>
> v3->v4:
> - patch 3 got much cleaner after BPF_KPTR_RCU was removed as suggested by David.
>
> [...]
Here is the summary with links:
- [v5,bpf-next,1/6] bpf: Rename __kptr_ref -> __kptr and __kptr -> __kptr_untrusted.
https://git.kernel.org/bpf/bpf-next/c/03b77e17aeb2
- [v5,bpf-next,2/6] bpf: Mark cgroups and dfl_cgrp fields as trusted.
https://git.kernel.org/bpf/bpf-next/c/8d093b4e95a2
- [v5,bpf-next,3/6] bpf: Introduce kptr_rcu.
https://git.kernel.org/bpf/bpf-next/c/20c09d92faee
- [v5,bpf-next,4/6] selftests/bpf: Add a test case for kptr_rcu.
https://git.kernel.org/bpf/bpf-next/c/838bd4ac9aa3
- [v5,bpf-next,5/6] selftests/bpf: Tweak cgroup kfunc test.
https://git.kernel.org/bpf/bpf-next/c/0047d8343f60
- [v5,bpf-next,6/6] bpf: Refactor RCU enforcement in the verifier.
https://git.kernel.org/bpf/bpf-next/c/6fcd486b3a0a
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:[~2023-03-03 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 4:14 [PATCH v5 bpf-next 0/6] bpf: Introduce kptr RCU Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 1/6] bpf: Rename __kptr_ref -> __kptr and __kptr -> __kptr_untrusted Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 2/6] bpf: Mark cgroups and dfl_cgrp fields as trusted Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 3/6] bpf: Introduce kptr_rcu Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 4/6] selftests/bpf: Add a test case for kptr_rcu Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 5/6] selftests/bpf: Tweak cgroup kfunc test Alexei Starovoitov
2023-03-03 4:14 ` [PATCH v5 bpf-next 6/6] bpf: Refactor RCU enforcement in the verifier Alexei Starovoitov
2023-03-03 14:22 ` David Vernet
2023-03-03 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=167786222035.26859.4386915483809485037.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=davem@davemloft.net \
--cc=davemarchevsky@meta.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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