From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
memxor@gmail.com
Subject: Re: [PATCH bpf-next v2 0/3] Remove KF_KPTR_GET kfunc flag
Date: Sun, 16 Apr 2023 16:00:18 +0000 [thread overview]
Message-ID: <168166081875.23493.14575067430091367699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230416084928.326135-1-void@manifault.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 16 Apr 2023 03:49:25 -0500 you wrote:
> We've managed to improve the UX for kptrs significantly over the last 9
> months. All of the existing use cases which previously had KF_KPTR_GET
> kfuncs (struct bpf_cpumask *, struct task_struct *, and struct cgroup *)
> have all been updated to be synchronized using RCU. In other words,
> their KF_KPTR_GET kfuncs have been removed in favor of KF_RCU |
> KF_ACQUIRE kfuncs, with the pointers themselves also being readable from
> maps in an RCU read region thanks to the types being RCU safe.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] bpf: Remove bpf_kfunc_call_test_kptr_get() test kfunc
https://git.kernel.org/bpf/bpf-next/c/09b501d90521
- [bpf-next,v2,2/3] bpf: Remove KF_KPTR_GET kfunc flag
https://git.kernel.org/bpf/bpf-next/c/7b4ddf3920d2
- [bpf-next,v2,3/3] bpf,docs: Remove KF_KPTR_GET from documentation
https://git.kernel.org/bpf/bpf-next/c/530474e6d044
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-04-16 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 8:49 [PATCH bpf-next v2 0/3] Remove KF_KPTR_GET kfunc flag David Vernet
2023-04-16 8:49 ` [PATCH bpf-next v2 1/3] bpf: Remove bpf_kfunc_call_test_kptr_get() test kfunc David Vernet
2023-04-16 8:49 ` [PATCH bpf-next v2 2/3] bpf: Remove KF_KPTR_GET kfunc flag David Vernet
2023-04-16 8:49 ` [PATCH bpf-next v2 3/3] bpf,docs: Remove KF_KPTR_GET from documentation David Vernet
2023-04-16 16:00 ` 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=168166081875.23493.14575067430091367699.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=yhs@fb.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