Mark Brown broonie@kernel.org writes:
Also, it's strange that the tests defined after map_gcs.stack_overflow don't run when I execute this test program. I'm doing:
$ ./run_kselftest.sh -t arm64:libc-gcs
I.e., these tests aren't being run in my FVP:
+FIXTURE_VARIANT_ADD(map_invalid_gcs, too_small) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_1) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_2) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_3) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_4) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_5) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_6) +FIXTURE_VARIANT_ADD(map_invalid_gcs, unligned_7) +TEST_F(map_invalid_gcs, do_map) +FIXTURE_VARIANT_ADD(invalid_mprotect, exec) +FIXTURE_VARIANT_ADD(invalid_mprotect, bti) +FIXTURE_VARIANT_ADD(invalid_mprotect, exec_bti) +TEST_F(invalid_mprotect, do_map) +TEST_F(invalid_mprotect, do_map_read)
I'm seeing all of those appearing. I'm not sure what to say there - that's all kselftest framework stuff, I'd expect the framework to say something about what it's doing if it decides to skip and I can't think why it would decide to skip.
Thanks. I'll poke some more to see if I can figure out what's going on.