From: Quentin Monnet <qmo@kernel.org>
To: Kenta Tada <tadakentaso@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH] bpftool: Query only cgroup-related attach types
Date: Wed, 29 May 2024 21:22:53 +0100 [thread overview]
Message-ID: <ce5befac-f227-4d2a-bf4b-14e8c7d49052@kernel.org> (raw)
In-Reply-To: <20240529131028.41200-1-tadakentaso@gmail.com>
On 29/05/2024 14:10, Kenta Tada wrote:
> When CONFIG_NETKIT=y,
> bpftool-cgroup shows error even if the cgroup's path is correct:
>
> $ bpftool cgroup tree /sys/fs/cgroup
> CgroupPath
> ID AttachType AttachFlags Name
> Error: can't query bpf programs attached to /sys/fs/cgroup: No such device or address
>
> From strace and kernel tracing, I found netkit returned ENXIO and this command failed.
> I think this AttachType(BPF_NETKIT_PRIMARY) is not relevant to cgroup.
>
> bpftool-cgroup should query just only cgroup-related attach types.
>
> Signed-off-by: Kenta Tada <tadakentaso@gmail.com>
> ---
> tools/bpf/bpftool/cgroup.c | 47 +++++++++++++++++++++++++++++++++-----
> 1 file changed, 41 insertions(+), 6 deletions(-)
>
> diff --git a/tools/bpf/bpftool/cgroup.c b/tools/bpf/bpftool/cgroup.c
> index af6898c0f388..bb2703aa4756 100644
> --- a/tools/bpf/bpftool/cgroup.c
> +++ b/tools/bpf/bpftool/cgroup.c
> @@ -19,6 +19,39 @@
>
> #include "main.h"
>
> +static const bool cgroup_attach_types[] = {
> + [BPF_CGROUP_INET_INGRESS] = true,
> + [BPF_CGROUP_INET_EGRESS] = true,
> + [BPF_CGROUP_INET_SOCK_CREATE] = true,
> + [BPF_CGROUP_INET_SOCK_RELEASE] = true,
> + [BPF_CGROUP_INET4_BIND] = true,
> + [BPF_CGROUP_INET6_BIND] = true,
> + [BPF_CGROUP_INET4_POST_BIND] = true,
> + [BPF_CGROUP_INET6_POST_BIND] = true,
> + [BPF_CGROUP_INET4_CONNECT] = true,
> + [BPF_CGROUP_INET6_CONNECT] = true,
> + [BPF_CGROUP_UNIX_CONNECT] = true,
> + [BPF_CGROUP_INET4_GETPEERNAME] = true,
> + [BPF_CGROUP_INET6_GETPEERNAME] = true,
> + [BPF_CGROUP_UNIX_GETPEERNAME] = true,
> + [BPF_CGROUP_INET4_GETSOCKNAME] = true,
> + [BPF_CGROUP_INET6_GETSOCKNAME] = true,
> + [BPF_CGROUP_UNIX_GETSOCKNAME] = true,
> + [BPF_CGROUP_UDP4_SENDMSG] = true,
> + [BPF_CGROUP_UDP6_SENDMSG] = true,
> + [BPF_CGROUP_UNIX_SENDMSG] = true,
> + [BPF_CGROUP_UDP4_RECVMSG] = true,
> + [BPF_CGROUP_UDP6_RECVMSG] = true,
> + [BPF_CGROUP_UNIX_RECVMSG] = true,
> + [BPF_CGROUP_SOCK_OPS] = true,
> + [BPF_CGROUP_DEVICE] = true,
> + [BPF_CGROUP_SYSCTL] = true,
> + [BPF_CGROUP_GETSOCKOPT] = true,
> + [BPF_CGROUP_SETSOCKOPT] = true,
> + [BPF_LSM_CGROUP] = true,
> + [__MAX_BPF_ATTACH_TYPE] = false,
> +};
Thanks for this!
I can't say I'm glad to see another version of the list of
cgroup-related attach types (in addition to HELP_SPEC_ATTACH_TYPES and
to the manual page). But the alternative would be to explicitly skip
BPF_NETKIT_PRIMARY, which is not great, either. Too bad we don't have a
way to check whether the type is cgroup-related in libbpf or from the
bpf.h headers; but I don't think there's much interest to add it there,
so we'll probably have the array. We should account for it in
tools/testing/selftests/bpf/test_bpftool_synctypes.py, but I can do this
as a follow-up if you don't feel like messing up with the Python script.
> +
> #define HELP_SPEC_ATTACH_FLAGS \
> "ATTACH_FLAGS := { multi | override }"
>
> @@ -187,14 +220,16 @@ static int cgroup_has_attached_progs(int cgroup_fd)
> bool no_prog = true;
>
> for (type = 0; type < __MAX_BPF_ATTACH_TYPE; type++) {
> - int count = count_attached_bpf_progs(cgroup_fd, type);
> + if (cgroup_attach_types[type]) {
Please change here:
int count;
if (!cgroup_attach_types[type])
continue;
And no need to further indent the rest of the block.
> + int count = count_attached_bpf_progs(cgroup_fd, type);
>
> - if (count < 0 && errno != EINVAL)
> - return -1;
> + if (count < 0 && errno != EINVAL)
> + return -1;
>
> - if (count > 0) {
> - no_prog = false;
> - break;
> + if (count > 0) {
> + no_prog = false;
> + break;
> + }
> }
> }
>
next prev parent reply other threads:[~2024-05-29 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 13:10 [PATCH] bpftool: Query only cgroup-related attach types Kenta Tada
2024-05-29 20:22 ` Quentin Monnet [this message]
2024-05-31 13:01 ` Kenta Tada
2024-05-30 21:20 ` Andrii Nakryiko
2024-05-31 13:03 ` Kenta Tada
2024-05-31 16:30 ` Andrii Nakryiko
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=ce5befac-f227-4d2a-bf4b-14e8c7d49052@kernel.org \
--to=qmo@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tadakentaso@gmail.com \
--cc=yonghong.song@linux.dev \
/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