From: patchwork-bot+netdevbpf@kernel.org
To: Hao Luo <haoluo@google.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
yhs@fb.com, acme@kernel.org, kpsingh@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v1 0/4] bpf: add __percpu tagging in vmlinux BTF
Date: Sun, 06 Mar 2022 02:50:11 +0000 [thread overview]
Message-ID: <164653501118.13752.451870897328051806.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220304191657.981240-1-haoluo@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Mar 2022 11:16:53 -0800 you wrote:
> This patchset is very much similar to Yonghong's patchset on adding
> __user tagging [1], where a "user" btf_type_tag was introduced to
> describe __user memory pointers. Similar approach can be applied on
> __percpu pointers. The __percpu attribute in kernel is used to identify
> pointers that point to memory allocated in percpu region. Normally,
> accessing __percpu memory requires using special functions like
> per_cpu_ptr() etc. Directly accessing __percpu pointer is meaningless.
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/4] bpf: Fix checking PTR_TO_BTF_ID in check_mem_access
https://git.kernel.org/bpf/bpf-next/c/bff61f6faedb
- [bpf-next,v1,2/4] compiler_types: define __percpu as __attribute__((btf_type_tag("percpu")))
https://git.kernel.org/bpf/bpf-next/c/9216c9162378
- [bpf-next,v1,3/4] bpf: Reject programs that try to load __percpu memory.
https://git.kernel.org/bpf/bpf-next/c/5844101a1be9
- [bpf-next,v1,4/4] selftests/bpf: Add a test for btf_type_tag "percpu"
https://git.kernel.org/bpf/bpf-next/c/50c6b8a9aea2
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:[~2022-03-06 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 19:16 [PATCH bpf-next v1 0/4] bpf: add __percpu tagging in vmlinux BTF Hao Luo
2022-03-04 19:16 ` [PATCH bpf-next v1 1/4] bpf: Fix checking PTR_TO_BTF_ID in check_mem_access Hao Luo
2022-03-05 20:00 ` Yonghong Song
2022-03-04 19:16 ` [PATCH bpf-next v1 2/4] compiler_types: define __percpu as __attribute__((btf_type_tag("percpu"))) Hao Luo
2022-03-05 20:06 ` Yonghong Song
2022-03-08 1:44 ` Andrii Nakryiko
2022-03-09 7:07 ` Yonghong Song
2022-03-09 19:31 ` Hao Luo
2022-03-04 19:16 ` [PATCH bpf-next v1 3/4] bpf: Reject programs that try to load __percpu memory Hao Luo
2022-03-05 21:15 ` Yonghong Song
2022-03-04 19:16 ` [PATCH bpf-next v1 4/4] selftests/bpf: Add a test for btf_type_tag "percpu" Hao Luo
2022-03-05 21:20 ` Yonghong Song
2022-03-06 2:49 ` Alexei Starovoitov
2022-03-08 1:41 ` Hao Luo
2022-03-06 2: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=164653501118.13752.451870897328051806.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=kpsingh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.