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
Subject: Re: [PATCH bpf-next v2 0/5] Make struct bpf_cpumask RCU safe
Date: Thu, 16 Mar 2023 19:40:19 +0000 [thread overview]
Message-ID: <167899561918.25671.10670272982001703575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230316054028.88924-1-void@manifault.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.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
prev parent reply other threads:[~2023-03-16 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 5:40 [PATCH bpf-next v2 0/5] Make struct bpf_cpumask RCU safe David Vernet
2023-03-16 5:40 ` [PATCH bpf-next v2 1/5] bpf: Free struct bpf_cpumask in call_rcu handler David Vernet
2023-03-16 5:40 ` [PATCH bpf-next v2 2/5] bpf: Mark struct bpf_cpumask as rcu protected David Vernet
2023-03-16 5:40 ` [PATCH bpf-next v2 3/5] bpf/selftests: Test using global cpumask kptr with RCU David Vernet
2023-03-16 5:40 ` [PATCH bpf-next v2 4/5] bpf: Remove bpf_cpumask_kptr_get() kfunc David Vernet
2023-03-16 5:40 ` [PATCH bpf-next v2 5/5] bpf,docs: Remove bpf_cpumask_kptr_get() from documentation David Vernet
2023-03-16 19:40 ` 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=167899561918.25671.10670272982001703575.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=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