From: Stanislav Fomichev <sdf@fomichev.me>
To: "Alexis Lothoré (eBPF Foundation)" <alexis.lothore@bootlin.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
ebpf@linuxfoundation.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] selftests/bpf: convert test_dev_cgroup to test_progs
Date: Mon, 29 Jul 2024 14:54:08 -0700 [thread overview]
Message-ID: <ZqgPgHjkW1KMPgu4@mini-arch> (raw)
In-Reply-To: <20240729-convert_dev_cgroup-v2-0-4c1fc0520545@bootlin.com>
On 07/29, Alexis Lothoré (eBPF Foundation) wrote:
> Hello,
> this small series aims to integrate test_dev_cgroup in test_progs so it
> could be run automatically in CI. The new version brings a few differences
> with the current one:
> - test now uses directly syscalls instead of wrapping commandline tools
> into system() calls
> - test_progs manipulates /dev/null (eg: redirecting test logs into it), so
> disabling access to it in the bpf program confuses the tests. To fix this,
> the first commit modifies the bpf program to allow access to char devices
> 1:3 (/dev/null), and disable access to char devices 1:5 (/dev/zero)
> - once test is converted, add a small subtest to also check for device type
> interpretation (char or block)
> - paths used in mknod tests are now in /dev instead of /tmp: due to the CI
> runner organisation and mountpoints manipulations, trying to create nodes
> in /tmp leads to errors unrelated to the test (ie, mknod calls refused by
> kernel, not the bpf program). I don't understand exactly the root cause
> at the deepest point (all I see in CI is an -ENXIO error on mknod when trying to
> create the node in tmp, and I can not make sense out of it neither
> replicate it locally), so I would gladly take inputs from anyone more
> educated than me about this.
>
> The new test_progs part has been tested in a local qemu environment as well
> as in upstream CI:
>
> ./test_progs -a cgroup_dev
> 47/1 cgroup_dev/deny-mknod:OK
> 47/2 cgroup_dev/allow-mknod:OK
> 47/3 cgroup_dev/deny-mknod-wrong-type:OK
> 47/4 cgroup_dev/allow-read:OK
> 47/5 cgroup_dev/allow-write:OK
> 47/6 cgroup_dev/deny-read:OK
> 47/7 cgroup_dev/deny-write:OK
> 47 cgroup_dev:OK
> Summary: 1/7 PASSED, 0 SKIPPED, 0 FAILED
>
> ---
> Changes in v2:
> - directly pass expected ret code to subtests instead of boolean pass/not
> pass
> - fix faulty fd check in subtest expected to fail on open
> - fix wrong subtest name
> - pass test buffer and corresponding size to read/write subtests
> - use correct series prefix
> - Link to v1: https://lore.kernel.org/r/20240725-convert_dev_cgroup-v1-0-2c8cbd487c44@bootlin.com
For the next respin (after addressing Alan's comment about
bpf_program__attach_cgroup):
Acked-by: Stanislav Fomichev <sdf@fomichev.me>
prev parent reply other threads:[~2024-07-29 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 8:20 [PATCH bpf-next v2 0/3] selftests/bpf: convert test_dev_cgroup to test_progs Alexis Lothoré (eBPF Foundation)
2024-07-29 8:20 ` [PATCH bpf-next v2 1/3] selftests/bpf: do not disable /dev/null device access in cgroup dev test Alexis Lothoré (eBPF Foundation)
2024-07-29 16:59 ` Alan Maguire
2024-07-29 17:30 ` Alexis Lothoré
2024-07-30 8:16 ` Alan Maguire
2024-07-30 8:42 ` Alexis Lothoré
2024-07-29 8:20 ` [PATCH bpf-next v2 2/3] selftests/bpf: convert test_dev_cgroup to test_progs Alexis Lothoré (eBPF Foundation)
2024-07-29 17:29 ` Alan Maguire
2024-07-29 17:47 ` Alexis Lothoré
2024-07-29 18:15 ` Alan Maguire
2024-07-29 8:20 ` [PATCH bpf-next v2 3/3] selftests/bpf: add wrong type test to cgroup dev Alexis Lothoré (eBPF Foundation)
2024-07-29 17:40 ` Alan Maguire
2024-07-29 21:54 ` Stanislav Fomichev [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=ZqgPgHjkW1KMPgu4@mini-arch \
--to=sdf@fomichev.me \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.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 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.