From: Pu Lehui <pulehui@huawei.com>
To: John Fastabend <john.fastabend@gmail.com>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Quentin Monnet <quentin@isovalent.com>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, KP Singh <kpsingh@kernel.org>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH bpf-next 1/2] bpf, cgroup: Fix attach flags being assigned to effective progs
Date: Thu, 8 Sep 2022 11:23:07 +0800 [thread overview]
Message-ID: <2985cda1-a443-8a9e-8f90-674b55159cb2@huawei.com> (raw)
In-Reply-To: <e726439f-0592-25c4-53e3-ce248940a736@huawei.com>
On 2022/9/8 11:07, Pu Lehui wrote:
>
>
> On 2022/8/24 5:22, John Fastabend wrote:
>> Pu Lehui wrote:
>>> Attach flags is only valid for attached progs of this layer cgroup,
>>> but not for effective progs. We know that the attached progs is at
>>> the beginning of the effective progs array, so we can just populate
>>> the elements in front of the prog_attach_flags array.
>>>
>>> Signed-off-by: Pu Lehui <pulehui@huawei.com>
>>
>> Trying to parse above, could you add a bit more detail on why this is
>> problem so readers don't need to track it down.
>>
>>> ---
>>> kernel/bpf/cgroup.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/kernel/bpf/cgroup.c b/kernel/bpf/cgroup.c
>>> index 59b7eb60d5b4..9adf72e99907 100644
>>> --- a/kernel/bpf/cgroup.c
>>> +++ b/kernel/bpf/cgroup.c
>>> @@ -1091,11 +1091,14 @@ static int __cgroup_bpf_query(struct cgroup
>>> *cgrp, const union bpf_attr *attr,
>>> }
>>
>> Because we are looking at it let me try to understand. There are two
>> paths that set cnt relative bits here,
>>
>
> Hi John,
>
> Thanks for your review. The reason is that:
> For the following cgroup tree:
> root
> |
> cg1
> |
> cg2
>
> I attached prog1 and prog2 to root cgroup with MULTI attach type,
sorry, typo, attach type -> attach flag
> attached prog3 to cg1 with OVERRIDE attach type, and then used bpftool
> to show this cgroup tree with effective query flag:
>
> $ bpftool cgroup tree /sys/fs/cgroup effective
> CgroupPath
> ID AttachType AttachFlags Name
> /sys/fs/cgroup
> 1 sysctl multi sysctl_tcp_mem
> 2 sysctl multi sysctl_tcp_mem
> /sys/fs/cgroup/cg1
> 3 sysctl override sysctl_tcp_mem
> 1 sysctl override sysctl_tcp_mem <- wrong
> 2 sysctl override sysctl_tcp_mem <- wrong
> /sys/fs/cgroup/cg1/cg2
> 3 sysctl sysctl_tcp_mem
> 1 sysctl sysctl_tcp_mem
> 2 sysctl sysctl_tcp_mem
>
> For cg1, obviously, the attach flags of prog1 and prog2 can not be
> OVERRIDE, and the attach flags of prog1 and prog2 is meaningless for
> cg1. We only need to care the attach flags of prog which attached to
> cg1, other progs attach flags should be omit.
>
>> if (attr->query.query_flags & BPF_F_QUERY_EFFECTIVE) {
>> ...
>> cnt = min_t(int, bpf_prog_array_length(effective), total_cnt);
>> ...
>> } else {
>> ...
>> progs = &cgrp->bpf.progs[atype];
>> cnt = min_t(int, prog_list_length(progs), total_cnt);
>> ...
>> }
>>
>> And the docs claim
>>
>> * **BPF_F_QUERY_EFFECTIVE**
>> * Only return information regarding programs
>> which are
>> * currently effective at the specified
>> *target_fd*.
>>
>> so in the EFFECTIVE case should we be reporting flags at all if the
>> commit message says "attach flags is only valid for attached progs
>> of this layer cgroup, but not for effective progs."
>>
>> And then in the else branch the change is what you have in the diff
>> anyways correct?
>>
>>> if (prog_attach_flags) {
>>> + int progs_cnt = prog_list_length(&cgrp->bpf.progs[atype]);
>>> flags = cgrp->bpf.flags[atype];
>>> - for (i = 0; i < cnt; i++)
>>
>> Do we need to min with total_cnt here so we don't walk off a short
>> user list?
>>
>
> We should limit it, will fix it in v2. For query without effective flag,
> progs_cnt will equal to cnt, and for effective flag situation, progs_cnt
> only calculate prog count which attached to this cgroup layer.
>
>>> + /* attach flags only for attached progs, but not
>>> effective progs */
>>> + for (i = 0; i < progs_cnt; i++)
>>> if (copy_to_user(prog_attach_flags + i, &flags,
>>> sizeof(flags)))
>>> return -EFAULT;
>>> +
>>> prog_attach_flags += cnt;
>>> }
>>> --
>>> 2.25.1
>>>
>> .
>>
> .
next prev parent reply other threads:[~2022-09-08 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 12:02 [PATCH bpf-next 0/2] Fix cgroup " Pu Lehui
2022-08-20 12:02 ` [PATCH bpf-next 1/2] bpf, cgroup: Fix " Pu Lehui
2022-08-23 21:22 ` John Fastabend
2022-09-08 3:07 ` Pu Lehui
2022-09-08 3:23 ` Pu Lehui [this message]
2022-08-20 12:02 ` [PATCH bpf-next 2/2] bpftool: Fix cgroup " Pu Lehui
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=2985cda1-a443-8a9e-8f90-674b55159cb2@huawei.com \
--to=pulehui@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--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
all inboxes | Powered by JetHome®