From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org
Subject: Re: [PATCH bpf-next v2 0/1] Refactor cgroup_bpf internals to use more specific attach_type
Date: Tue, 24 Aug 2021 01:00:05 +0000 [thread overview]
Message-ID: <162976680558.16394.17738506707111563389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210819092420.1984861-1-davemarchevsky@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 19 Aug 2021 02:24:19 -0700 you wrote:
> The cgroup_bpf struct has a few arrays (effective, progs, and flags) of
> size MAX_BPF_ATTACH_TYPE. These are meant to separate progs by their
> attach type, currently represented by the bpf_attach_type enum.
>
> There are some bpf_attach_type values which are not valid attach types
> for cgroup bpf programs. Programs with these attach types will never be
> handled by cgroup_bpf_{attach,detach} and thus will never be held in
> cgroup_bpf structs. Even if such programs did make it into their
> reserved slot in those arrays, they would never be executed.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/1] bpf: migrate cgroup_bpf to internal cgroup_bpf_attach_type enum
https://git.kernel.org/bpf/bpf-next/c/4ed589a27893
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:[~2021-08-24 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 9:24 [PATCH bpf-next v2 0/1] Refactor cgroup_bpf internals to use more specific attach_type Dave Marchevsky
2021-08-19 9:24 ` [PATCH bpf-next v2 1/1] bpf: migrate cgroup_bpf to internal cgroup_bpf_attach_type enum Dave Marchevsky
2021-08-24 1:00 ` 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=162976680558.16394.17738506707111563389.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@fb.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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