[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167899561918.25671.10670272982001703575.git-patchwork-notify@kernel.org>
Date: Thu, 16 Mar 2023 19:40:19 +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
Subject: Re: [PATCH bpf-next v2 0/5] Make struct bpf_cpumask RCU safe
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Thu, 16 Mar 2023 00:40:23 -0500 you wrote:
> The struct bpf_cpumask type is currently not RCU safe. It uses the
> bpf_mem_cache_{alloc,free}() APIs to allocate and release cpumasks, and
> those allocations may be reused before an RCU grace period has elapsed.
> We want to be able to enable using this pattern in BPF programs:
>
> private(MASK) static struct bpf_cpumask __kptr *global;
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/5] bpf: Free struct bpf_cpumask in call_rcu handler
https://git.kernel.org/bpf/bpf-next/c/77473d1a962f
- [bpf-next,v2,2/5] bpf: Mark struct bpf_cpumask as rcu protected
https://git.kernel.org/bpf/bpf-next/c/63d2d83d21a6
- [bpf-next,v2,3/5] bpf/selftests: Test using global cpumask kptr with RCU
https://git.kernel.org/bpf/bpf-next/c/a5a197df58c4
- [bpf-next,v2,4/5] bpf: Remove bpf_cpumask_kptr_get() kfunc
https://git.kernel.org/bpf/bpf-next/c/1b403ce77dfb
- [bpf-next,v2,5/5] bpf,docs: Remove bpf_cpumask_kptr_get() from documentation
https://git.kernel.org/bpf/bpf-next/c/fec2c6d14fd5
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