[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168166081875.23493.14575067430091367699.git-patchwork-notify@kernel.org>
Date: Sun, 16 Apr 2023 16:00:18 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Vernet <void@...ifault.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
linux-kernel@...r.kernel.org, kernel-team@...a.com,
memxor@...il.com
Subject: Re: [PATCH bpf-next v2 0/3] Remove KF_KPTR_GET kfunc flag
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.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
Powered by blists - more mailing lists