selftests/bpf: convert test_dev_cgroup to test_progs
Subsystems (3)
v2 cover selftests/bpf: convert test_dev_cgroup to test_progs
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/[email protected]
---
Alexis Lothoré (eBPF Foundation) (3):
selftests/bpf: do not disable /dev/null device access in cgroup dev test selftests/bpf: convert test_dev_cgroup to test_progs selftests/bpf: add wrong type test to cgroup dev
tools/testing/selftests/bpf/.gitignore | 1 - tools/testing/selftests/bpf/Makefile | 2 - .../testing/selftests/bpf/prog_tests/cgroup_dev.c | 113 +++++++++++++++++++++ tools/testing/selftests/bpf/progs/dev_cgroup.c | 4 +- tools/testing/selftests/bpf/test_dev_cgroup.c | 85 ---------------- 5 files changed, 115 insertions(+), 90 deletions(-)
---
base-commit: 3e9fef7751a84a7d02bbe14a67d3a5d301cbd156
change-id: 20240723-convert_dev_cgroup-6464b0d37f1a
Best regards,
Signature · 3 lines
Alexis Lothoré, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH v2 1/3 selftests/bpf: do not disable /dev/null device access in cgroup dev test
test_dev_cgroup currently loads a small bpf program allowing any access on urandom and zero devices, disabling access to any other device. It makes migrating this test to test_progs impossible, since this one manipulates extensively /dev/null.
Allow /dev/null manipulation in dev_cgroup program to make its usage in test_progs framework possible. Update test_dev_cgroup.c as well to match this change while it has not been removed.
--- tools/testing/selftests/bpf/progs/dev_cgroup.c | 4 ++-- tools/testing/selftests/bpf/test_dev_cgroup.c | 18 +++++++++--------- 2 files changed, 11 insertions(+), 11 deletions(-)
tools/testing/selftests/bpf/progs/dev_cgroup.c +2 -2
@@ -41,14 +41,14 @@ int bpf_prog1(struct bpf_cgroup_dev_ctx *ctx)bpf_trace_printk (fmt,sizeof (fmt), ctx->major, ctx->minor);#endif -/* Allow access to /dev/zero and /dev/random. +/* Allow access to /dev/null and /dev/urandom. * Forbid everything else. */ if (ctx->major !=1 || type !=BPF_DEVCG_DEV_CHAR )return 0 ;switch (ctx->minor) { -case 5 :/* 1:5 /dev/zero */ +case 3 :/* 1:3 /dev/null */ case 9 :/* 1:9 /dev/urandom */ return 1 ; }
tools/testing/selftests/bpf/test_dev_cgroup.c +9 -9
@@ -54,25 +54,25 @@ int main(int argc, char **argv) goto err; } -/* All operations with /dev/zero and and /dev/urandom are allowed, +/* All operations with /dev/null and /dev/urandom are allowed, * everything else is forbidden. */ -assert (system ("rm -f /tmp/test_dev_cgroup_null" ) ==0 ); -assert (system ("mknod /tmp/test_dev_cgroup_null c 1 3" )); -assert (system ("rm -f /tmp/test_dev_cgroup_null" ) ==0 ); - -/* /dev/zero is whitelisted */ assert (system ("rm -f /tmp/test_dev_cgroup_zero" ) ==0 ); -assert (system ("mknod /tmp/test_dev_cgroup_zero c 1 5" ) ==0 ); +assert (system ("mknod /tmp/test_dev_cgroup_zero c 1 5" ));assert (system ("rm -f /tmp/test_dev_cgroup_zero" ) ==0 ); -assert (system ("dd if=/dev/urandom of=/dev/zero count=64" ) ==0 ); +/* /dev/null is whitelisted */ +assert (system ("rm -f /tmp/test_dev_cgroup_null" ) ==0 ); +assert (system ("mknod /tmp/test_dev_cgroup_null c 1 3" ) ==0 ); +assert (system ("rm -f /tmp/test_dev_cgroup_null" ) ==0 ); + +assert (system ("dd if=/dev/urandom of=/dev/null count=64" ) ==0 );/* src is allowed, target is forbidden */ assert (system ("dd if=/dev/urandom of=/dev/full count=64" ));/* src is forbidden, target is allowed */ -assert (system ("dd if=/dev/random of=/dev/zero count=64" )); +assert (system ("dd if=/dev/random of=/dev/null count=64" )); error =0 ;printf ("test_dev_cgroup:PASS\n" );
Signature · 1 line
2.45.2
Re: [PATCH bpf-next v2 1/3] selftests/bpf: do not disable /dev/null device access in cgroup dev test
Quoted 5 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupcurrently loads a small bpf program allowing any access on urandom and zero devices, disabling access to any other device. It makes migrating this test totest_progsimpossible, since this one manipulates extensively/dev/null.
Quoted 8 lines
Allow
/dev/nullmanipulation indev_cgroupprogram to make its usage intest_progsframework possible. Updatetest_dev_cgroup.cas well to match this change while it has not been removed.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>--- tools/testing/selftests/bpf/progs/dev_cgroup.c | 4 ++-- tools/testing/selftests/bpf/test_dev_cgroup.c | 18 +++++++++---------
Not a big deal, but I found it a bit confusing that this file was modified then deleted in patch 2. Would it work having patch 1 stop building the standalone test/remove it and .gitignore entry, patch 2 updating progs/dev_cgroup.c to allow /dev/zero, /dev/urandom access, patch 3 add cgroup_dev.c test support, and patch 4 add the device type subtest? Or are there issues with doing things that way? Thanks!
Alan
Re: [PATCH bpf-next v2 1/3] selftests/bpf: do not disable /dev/null device access in cgroup dev test
Hello Alan,
Quoted 15 lines · Alan Maguire
Quoted 5 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupcurrently loads a small bpf program allowing any access on urandom and zero devices, disabling access to any other device. It makes migrating this test totest_progsimpossible, since this one manipulates extensively/dev/null.Quoted 8 lines
Allow
/dev/nullmanipulation indev_cgroupprogram to make its usage intest_progsframework possible. Updatetest_dev_cgroup.cas well to match this change while it has not been removed.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>--- tools/testing/selftests/bpf/progs/dev_cgroup.c | 4 ++-- tools/testing/selftests/bpf/test_dev_cgroup.c | 18 +++++++++---------
Quoted 6 lines
Not a big deal, but I found it a bit confusing that this file was modified then deleted in patch 2. Would it work having patch 1 stop building the standalone test/remove it and .gitignore entry, patch 2 updating
progs/dev_cgroup.cto allow/dev/zero,/dev/urandomaccess, patch 3 addcgroup_dev.ctest support, and patch 4 add the device type subtest? Or are there issues with doing things that way? Thanks!
I've done this to make sure that at any point in the git history, there is one working test for the targeted feature, either the old or the new one. I've done it this way because the old test also helped me validate the new one while developing it, but also because if at some point there is a (major) issue with the new test, reverting only the relevant commit brings back the old test while disabling the new one.
But maybe this concern is not worth the trouble (especially since the old tests are not run automatically) ? If that's indeed the case, I can do it the way you are suggesting :)
Thanks,
Alexis
Signature · 3 lines
Alexis Lothoré, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [PATCH bpf-next v2 1/3] selftests/bpf: do not disable /dev/null device access in cgroup dev test
Quoted 32 lines · Alexis Lothoré
Hello Alan,
Quoted 15 lines · Alan Maguire
Quoted 5 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupcurrently loads a small bpf program allowing any access on urandom and zero devices, disabling access to any other device. It makes migrating this test totest_progsimpossible, since this one manipulates extensively/dev/null.Quoted 8 lines
Allow
/dev/nullmanipulation indev_cgroupprogram to make its usage intest_progsframework possible. Updatetest_dev_cgroup.cas well to match this change while it has not been removed.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>--- tools/testing/selftests/bpf/progs/dev_cgroup.c | 4 ++-- tools/testing/selftests/bpf/test_dev_cgroup.c | 18 +++++++++---------Quoted 6 lines
Not a big deal, but I found it a bit confusing that this file was modified then deleted in patch 2. Would it work having patch 1 stop building the standalone test/remove it and .gitignore entry, patch 2 updating
progs/dev_cgroup.cto allow/dev/zero,/dev/urandomaccess, patch 3 addcgroup_dev.ctest support, and patch 4 add the device type subtest? Or are there issues with doing things that way? Thanks!I've done this to make sure that at any point in the git history, there is one working test for the targeted feature, either the old or the new one. I've done it this way because the old test also helped me validate the new one while developing it, but also because if at some point there is a (major) issue with the new test, reverting only the relevant commit brings back the old test while disabling the new one.
Quoted 4 lines
But maybe this concern is not worth the trouble (especially since the old tests are not run automatically) ? If that's indeed the case, I can do it the way you are suggesting :)
If no-one complains, it seems fine to me to stick with the way you've constructed the series the next respin. Thanks!
Quoted 4 lines
Thanks,
Alexis
Re: [PATCH bpf-next v2 1/3] selftests/bpf: do not disable /dev/null device access in cgroup dev test
Quoted 2 lines · Alan Maguire
Quoted 1 line · Alexis Lothoré
Hello Alan,
[...]
Quoted 14 lines
Quoted 14 lines
Quoted 6 lines
Not a big deal, but I found it a bit confusing that this file was modified then deleted in patch 2. Would it work having patch 1 stop building the standalone test/remove it and .gitignore entry, patch 2 updating
progs/dev_cgroup.cto allow/dev/zero,/dev/urandomaccess, patch 3 addcgroup_dev.ctest support, and patch 4 add the device type subtest? Or are there issues with doing things that way? Thanks!I've done this to make sure that at any point in the git history, there is one working test for the targeted feature, either the old or the new one. I've done it this way because the old test also helped me validate the new one while developing it, but also because if at some point there is a (major) issue with the new test, reverting only the relevant commit brings back the old test while disabling the new one.
Quoted 7 lines
Quoted 4 lines
But maybe this concern is not worth the trouble (especially since the old tests are not run automatically) ? If that's indeed the case, I can do it the way you are suggesting :)
If no-one complains, it seems fine to me to stick with the way you've constructed the series the next respin. Thanks!
ACK, thanks, I'll keep it that way then.
For the record, I am accumulating a few other converted tests that I will send soon, and those follow the same logic (keeping one working test at any point of time, and pushing it to the point where I start by fixing broken tests before converting those), so if anyone has an opinion in favor of this or rather in favor of Alan's suggestion, do not hesitate to share it, so I can adjust before sending.
Thanks,
Quoted 6 lines
Quoted 5 lines
Thanks,
Alexis
Signature · 3 lines
Alexis Lothoré, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH v2 2/3 selftests/bpf: convert test_dev_cgroup to test_progs
In reply to Alexis Lothoré (eBPF Foundation)test_dev_cgroup is defined as a standalone test program, and so is not executed in CI.
Convert it to test_progs framework so it is tested automatically in CI, and remove the old test. In order to be able to run it in test_progs, /dev/null must remain usable, so change the new test to test operations on devices 1:3 as valid, and operations on devices 1:5 (/dev/zero) as invalid.
---
Changes in v2:
- pass expected return code to subtest function instead of boolean pass/not pass
- also pass buffer and buffer size for read/write subtests
- fix faulty fd check on read/write tests expected to fail
--- tools/testing/selftests/bpf/.gitignore | 1 - tools/testing/selftests/bpf/Makefile | 2 - .../testing/selftests/bpf/prog_tests/cgroup_dev.c | 110 +++++++++++++++++++++ tools/testing/selftests/bpf/test_dev_cgroup.c | 85 ---------------- 4 files changed, 110 insertions(+), 88 deletions(-)
tools/testing/selftests/bpf/.gitignore +0 -1
@@ -9,7 +9,6 @@ test_lpm_map test_tag FEATURE-DUMP.libbpf fixdep -test_dev_cgroup /test_progs /test_progs-no_alu32 /test_progs-bpf_gcc
tools/testing/selftests/bpf/Makefile +0 -2
@@ -69,7 +69,6 @@ endif # Order correspond to 'make run_tests' order TEST_GEN_PROGS = test_verifier test_tag test_maps test_lru_map test_lpm_map test_progs \ - test_dev_cgroup \ test_sock test_sockmap get_cgroup_id_user \ test_cgroup_storage \ test_tcpnotify_user test_sysctl \
@@ -295,7 +294,6 @@ JSON_WRITER := $(OUTPUT)/json_writer.o CAP_HELPERS := $(OUTPUT)/cap_helpers.o NETWORK_HELPERS := $(OUTPUT)/network_helpers.o -$(OUTPUT)/test_dev_cgroup: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_skb_cgroup_id_user: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_sock: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_sockmap: $(CGROUP_HELPERS) $(TESTING_HELPERS)
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +110 -0
110 lines not on this page · raw message
tools/testing/selftests/bpf/test_dev_cgroup.c deleted +0 -85
85 lines not on this page · raw message
Signature · 1 line
2.45.2
Quoted 9 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupis defined as a standalone test program, and so is not executed in CI.Convert it to
test_progsframework so it is tested automatically in CI, and remove the old test. In order to be able to run it intest_progs,/dev/nullmust remain usable, so change the new test to test operations on devices 1:3 as valid, and operations on devices 1:5 (/dev/zero) as invalid.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>
A few small suggestions but looks great!
Quoted 60 lines
---
Changes in v2:
- pass expected return code to subtest function instead of boolean pass/not pass
- also pass buffer and buffer size for read/write subtests
- fix faulty fd check on read/write tests expected to fail--- tools/testing/selftests/bpf/.gitignore | 1 - tools/testing/selftests/bpf/Makefile | 2 - .../testing/selftests/bpf/prog_tests/cgroup_dev.c | 110 +++++++++++++++++++++ tools/testing/selftests/bpf/test_dev_cgroup.c | 85 ---------------- 4 files changed, 110 insertions(+), 88 deletions(-)tools/testing/selftests/bpf/.gitignore +0
-1@@ -9,7 +9,6 @@ test_lpm_map test_tag FEATURE-DUMP.libbpf fixdep -test_dev_cgroup /test_progs /test_progs-no_alu32 /test_progs-bpf_gcctools/testing/selftests/bpf/Makefile +0
-2@@ -69,7 +69,6 @@ endif # Order correspond to 'make run_tests' order TEST_GEN_PROGS = test_verifier test_tag test_maps test_lru_map test_lpm_map test_progs \ - test_dev_cgroup \ test_sock test_sockmap get_cgroup_id_user \ test_cgroup_storage \ test_tcpnotify_user test_sysctl \@@ -295,7 +294,6 @@ JSON_WRITER := $(OUTPUT)/json_writer.o CAP_HELPERS := $(OUTPUT)/cap_helpers.o NETWORK_HELPERS := $(OUTPUT)/network_helpers.o -$(OUTPUT)/test_dev_cgroup: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_skb_cgroup_id_user: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_sock: $(CGROUP_HELPERS) $(TESTING_HELPERS) $(OUTPUT)/test_sockmap: $(CGROUP_HELPERS) $(TESTING_HELPERS)tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +9
-0@@ -0,0 +1,110 @@ +// SPDX-License-Identifier: GPL-2.0 + +#include <sys/stat.h> +#include <sys/sysmacros.h> +#include "test_progs.h" +#include "cgroup_helpers.h" +#include "dev_cgroup.skel.h" + +#define TEST_CGROUP "/test-bpf-based-device-cgroup/"
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 19
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +10
-0+#define TEST_BUFFER_SIZE 64 + +static void test_mknod (const char *path,mode_t mode,int dev_major, +int dev_minor,int expected_ret) +{ +int ret; + +unlink (path); + ret =mknod (path, mode,makedev (dev_major, dev_minor)); +ASSERT_EQ (ret, expected_ret,"mknod" );
no need to unlink unless "if (!ret)"
Quoted 56 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +56
-0+unlink (path); +} + +static void test_read (const char *path,char *buf,int buf_size,int expected_ret) +{ +int ret, fd; + + fd =open (path,O_RDONLY ); + +/* A bare open on unauthorized device should fail */ +if (expected_ret <0 ) { +ASSERT_EQ (fd, expected_ret,"open file for read" ); +if (fd >=0 ) +close (fd); +return ; + } + +if (!ASSERT_OK_FD (fd,"open file for read" )) +return ; + + ret =read (fd, buf, buf_size); +ASSERT_EQ (ret, expected_ret,"read" ); + +close (fd); +} + +static void test_write (const char *path,char *buf,int buf_size,int expected_ret) +{ +int ret, fd; + + fd =open (path,O_WRONLY ); + +/* A bare open on unauthorized device should fail */ +if (expected_ret <0 ) { +ASSERT_EQ (fd, expected_ret,"open file for write" ); +if (fd >=0 ) +close (fd); +return ; + } + +if (!ASSERT_OK_FD (fd,"open file for write" )) +return ; + + ret =write (fd, buf, buf_size); +ASSERT_EQ (ret, expected_ret,"write" ); + +close (fd); +} + +void test_cgroup_dev (void ) +{ +char buf[TEST_BUFFER_SIZE ] ="some random test data" ; +struct dev_cgroup *skel; +int cgroup_fd; + + cgroup_fd =cgroup_setup_and_join (TEST_CGROUP );
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 85
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +10
-0+if (!ASSERT_OK_FD (cgroup_fd,"cgroup switch" )) +return ; + + skel =dev_cgroup__open_and_load (); +if (!ASSERT_OK_PTR (skel,"load program" )) + goto cleanup_cgroup; + +if (!ASSERT_OK (bpf_prog_attach (bpf_program__fd (skel->progs.bpf_prog1), + cgroup_fd,BPF_CGROUP_DEVICE ,0 ), +"attach_program" ))
I'd suggest using bpf_program__attach_cgroup() here as you can assign the link in the skeleton; see prog_tests/cgroup_v1v2.c.
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 90
Quoted 5 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +5
-0+ goto cleanup_progs; + +if (test__start_subtest ("deny-mknod" )) +test_mknod ("/dev/test_dev_cgroup_zero" ,S_IFCHR ,1 ,5 , -EPERM ); +
nit: group with other deny subtests.
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 96
Quoted 6 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +6
-0+if (test__start_subtest ("allow-mknod" )) +test_mknod ("/dev/test_dev_cgroup_null" ,S_IFCHR ,1 ,3 ,0 ); + +if (test__start_subtest ("allow-read" )) +test_read ("/dev/urandom" , buf,TEST_BUFFER_SIZE ,TEST_BUFFER_SIZE ); +
Nit: should we have a separate garbage buffer for the successful /dev/urandom read? We're not validating buffer contents anywhere but we will overwrite our test string I think and it'll end up non-null terminated.
Alan
Hello Alan, thanks for the review
Quoted 14 lines · Alan Maguire
Quoted 9 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupis defined as a standalone test program, and so is not executed in CI.Convert it to
test_progsframework so it is tested automatically in CI, and remove the old test. In order to be able to run it intest_progs,/dev/nullmust remain usable, so change the new test to test operations on devices 1:3 as valid, and operations on devices 1:5 (/dev/zero) as invalid.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>A few small suggestions but looks great!
Reviewed-by Alan Maguire <[email protected]>
[...]
Quoted 4 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 19
Quoted 3 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +3
-0+unlink (path); + ret =mknod (path, mode,makedev (dev_major, dev_minor)); +ASSERT_EQ (ret, expected_ret,"mknod" );no need to unlink unless "if (!ret)"
Indeed, you are right.
[...]
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 85
Quoted 7 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +7
-0+ skel =dev_cgroup__open_and_load (); +if (!ASSERT_OK_PTR (skel,"load program" )) + goto cleanup_cgroup; + +if (!ASSERT_OK (bpf_prog_attach (bpf_program__fd (skel->progs.bpf_prog1), + cgroup_fd,BPF_CGROUP_DEVICE ,0 ), +"attach_program" ))I'd suggest using
bpf_program__attach_cgroup()here as you can assign the link in the skeleton; seeprog_tests/cgroup_v1v2.c.
Ah yes, thanks for the hint !
Quoted 7 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 90
Quoted 5 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +5
-0+ goto cleanup_progs; + +if (test__start_subtest ("deny-mknod" )) +test_mknod ("/dev/test_dev_cgroup_zero" ,S_IFCHR ,1 ,5 , -EPERM ); +nit: group with other deny subtests.
ACK
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 96
Quoted 6 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +6
-0+if (test__start_subtest ("allow-mknod" )) +test_mknod ("/dev/test_dev_cgroup_null" ,S_IFCHR ,1 ,3 ,0 ); + +if (test__start_subtest ("allow-read" )) +test_read ("/dev/urandom" , buf,TEST_BUFFER_SIZE ,TEST_BUFFER_SIZE ); +Nit: should we have a separate garbage buffer for the successful
/dev/urandomread? We're not validating buffer contents anywhere but we will overwrite our test string I think and it'll end up non-null terminated.
True, but since the tests aren't performing any string operation on it, is it really a big deal ? I can even switch the string to a byte array, if it can prevent any mistake.
If that's ok for you, I can bring all the suggestions discussed here in a new revision and keep your review tag.
Thanks,
Alexis
Quoted 2 lines
Alan
Signature · 3 lines
Alexis Lothoré, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 64 lines · Alexis Lothoré
Hello Alan, thanks for the review
Quoted 14 lines · Alan Maguire
Quoted 9 lines · Alexis Lothoré (eBPF Foundation)
test_dev_cgroupis defined as a standalone test program, and so is not executed in CI.Convert it to
test_progsframework so it is tested automatically in CI, and remove the old test. In order to be able to run it intest_progs,/dev/nullmust remain usable, so change the new test to test operations on devices 1:3 as valid, and operations on devices 1:5 (/dev/zero) as invalid.Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>A few small suggestions but looks great!
Reviewed-by Alan Maguire <[email protected]>[...]
Quoted 4 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 19
Quoted 3 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +3
-0+unlink (path); + ret =mknod (path, mode,makedev (dev_major, dev_minor)); +ASSERT_EQ (ret, expected_ret,"mknod" );no need to unlink unless "if (!ret)"
Indeed, you are right.
[...]
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 85
Quoted 7 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +7
-0+ skel =dev_cgroup__open_and_load (); +if (!ASSERT_OK_PTR (skel,"load program" )) + goto cleanup_cgroup; + +if (!ASSERT_OK (bpf_prog_attach (bpf_program__fd (skel->progs.bpf_prog1), + cgroup_fd,BPF_CGROUP_DEVICE ,0 ), +"attach_program" ))I'd suggest using
bpf_program__attach_cgroup()here as you can assign the link in the skeleton; seeprog_tests/cgroup_v1v2.c.Ah yes, thanks for the hint !
Quoted 7 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 90
Quoted 5 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +5
-0+ goto cleanup_progs; + +if (test__start_subtest ("deny-mknod" )) +test_mknod ("/dev/test_dev_cgroup_zero" ,S_IFCHR ,1 ,5 , -EPERM ); +nit: group with other deny subtests.
ACK
Quoted 10 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c line 96
Quoted 6 lines
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c new file +6
-0+if (test__start_subtest ("allow-mknod" )) +test_mknod ("/dev/test_dev_cgroup_null" ,S_IFCHR ,1 ,3 ,0 ); + +if (test__start_subtest ("allow-read" )) +test_read ("/dev/urandom" , buf,TEST_BUFFER_SIZE ,TEST_BUFFER_SIZE ); +Nit: should we have a separate garbage buffer for the successful
/dev/urandomread? We're not validating buffer contents anywhere but we will overwrite our test string I think and it'll end up non-null terminated.
Quoted 4 lines
True, but since the tests aren't performing any string operation on it, is it really a big deal ? I can even switch the string to a byte array, if it can prevent any mistake.
There's no need, don't worry. As long as the size limits ensure we don't overrun the buffer, we're good.
Quoted 3 lines
If that's ok for you, I can bring all the suggestions discussed here in a new revision and keep your review tag.
Sounds great, thanks!
Alan
PATCH v2 3/3 selftests/bpf: add wrong type test to cgroup dev
In reply to Alexis Lothoré (eBPF Foundation)Current cgroup_dev test mostly tests that device operation is accepted or refused base on passed major/minor (and so, any operation performed during test involves only char device)
Add a small subtest ensuring that the device type passed to bpf program allows it to take decisions as well.
---
Changes in v2:
- change test name ("null" block device does not make sense)
- use updated subtest API for this new subtest
--- tools/testing/selftests/bpf/prog_tests/cgroup_dev.c | 3 +++ 1 file changed, 3 insertions(+)
tools/testing/selftests/bpf/prog_tests/cgroup_dev.c +3 -0
@@ -91,6 +91,9 @@ void test_cgroup_dev(void)if (test__start_subtest ("allow-mknod" ))test_mknod ("/dev/test_dev_cgroup_null" ,S_IFCHR ,1 ,3 ,0 ); +if (test__start_subtest ("deny-mknod-wrong-type" )) +test_mknod ("/dev/test_dev_cgroup_block" ,S_IFBLK ,1 ,3 , -EPERM ); +if (test__start_subtest ("allow-read" ))test_read ("/dev/urandom" , buf,TEST_BUFFER_SIZE ,TEST_BUFFER_SIZE );
Signature · 1 line
2.45.2
Re: [PATCH bpf-next v2 3/3] selftests/bpf: add wrong type test to cgroup dev
Quoted 8 lines · Alexis Lothoré (eBPF Foundation)
Current
cgroup_devtest mostly tests that device operation is accepted or refused base on passed major/minor (and so, any operation performed during test involves only char device)Add a small subtest ensuring that the device type passed to bpf program allows it to take decisions as well.
Signed-off-by Alexis Lothoré (eBPF Foundation) <[email protected]>
Quoted 23 lines
---
Changes in v2:
- change test name ("null" block device does not make sense)
- use updated subtest API for this new subtest--- tools/testing/selftests/bpf/prog_tests/cgroup_dev.c | 3 +++ 1 file changed, 3 insertions(+)tools/testing/selftests/bpf/prog_tests/cgroup_dev.c +3
-0@@ -91,6 +91,9 @@ void test_cgroup_dev(void)if (test__start_subtest ("allow-mknod" ))test_mknod ("/dev/test_dev_cgroup_null" ,S_IFCHR ,1 ,3 ,0 ); +if (test__start_subtest ("deny-mknod-wrong-type" )) +test_mknod ("/dev/test_dev_cgroup_block" ,S_IFBLK ,1 ,3 , -EPERM ); +if (test__start_subtest ("allow-read" ))test_read ("/dev/urandom" , buf,TEST_BUFFER_SIZE ,TEST_BUFFER_SIZE );
Quoted 35 lines · Alexis Lothoré (eBPF Foundation)
Hello,
this small series aims to integratetest_dev_cgroupintest_progsso 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 intosystem()calls
-test_progsmanipulates/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-ENXIOerror 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_progspart has been tested in a local qemu environment as well as in upstream CI:./test_progs -a
cgroup_dev47/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:OKSummary: 1/7 PASSED, 0 SKIPPED, 0 FAILED
Quoted 9 lines
---
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/[email protected]
For the next respin (after addressing Alan's comment about bpf_program__attach_cgroup):