From: patchwork-bot+netdevbpf@kernel.org
To: Tejun Heo <tj@kernel.org>
Cc: 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, bpf@vger.kernel.org,
davemarchevsky@meta.com, void@manifault.com,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next] bpf: Make bpf_get_current_[ancestor_]cgroup_id() available for all program types
Date: Fri, 03 Mar 2023 06:40:18 +0000 [thread overview]
Message-ID: <167782561844.15961.8030839288480908972.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZAD8QyoszMZiTzBY@slm.duckdns.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 2 Mar 2023 09:42:59 -1000 you wrote:
> These helpers are safe to call from any context and there's no reason to
> restrict access to them. Remove them from bpf_trace and filter lists and add
> to bpf_base_func_proto() under perfmon_capable().
>
> v2: After consulting with Andrii, relocated in bpf_base_func_proto() so that
> they require bpf_capable() but not perfomon_capable() as it doesn't read
> from or affect others on the system.
>
> [...]
Here is the summary with links:
- [v2,bpf-next] bpf: Make bpf_get_current_[ancestor_]cgroup_id() available for all program types
https://git.kernel.org/bpf/bpf-next/c/c501bf55c88b
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-03 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 18:58 [PATCH bpf-next] bpf: Make bpf_get_current_[ancestor_]cgroup_id() available for all program types Tejun Heo
2023-03-02 19:42 ` [PATCH v2 " Tejun Heo
2023-03-03 6: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=167782561844.15961.8030839288480908972.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=davemarchevsky@meta.com \
--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=tj@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