On Wed, May 13, 2026 at 12:52:35PM +0200, Mickaël Salaün wrote: (...) > > > config: x86_64-rhel-9.4-kselftests > > > compiler: gcc-14 > > > test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with > > > 32G memory > > > > > > (please refer to attached dmesg/kmsg for entire log/backtrace) > > > > > > If you fix the issue in a separate patch/commit (i.e. not just a new > > > version of > > > the same patch/commit), kindly add following tags > > > | Reported-by: kernel test robot <[email protected]> > > > | Closes: > > > https://lore.kernel.org/oe-lkp/[email protected] > > > > I was unable to run the landlock selftests myself, on my machines they are > > failing at runtime with all kinds of colorful errors. Are the requirements > > explained somewhere? > > I'm curious about the errors you get. They are standard kselftests that > should work following this workflow: > > make TARGETS=landlock O=build kselftest-gen_tar > > and then running ./build/kselftests/kselftest_install/run_kselftest.sh > as root in a VM. The required kernel configuration is listed in > tools/testing/selftests/landlock/config
So there are two root issues I ran into: 1) The tests can not be executed from virtiofs (as set up by virtme-ng): # RUN audit.layers ... # audit_test.c:52:layers:Expected 0 (0) <= self->audit_fd (-13) # audit_test.c:61:layers:Failed to initialize audit: Permission denied # layers: Test failed # FAIL audit.layers not ok 1 audit.layers (The same for all other testcases) 2) $PWD needs to be the test binary directory for "./wait-pipe-sandbox" to work. > To make it easier, we wrote a wrapper to test everything with UML: > https://github.com/landlock-lsm/landlock-test-tools (see check-linux.sh) > > > > > > # # RUN audit.tsync_override_log_subdomains_off ... > > > # # audit_test.c:591:tsync_override_log_subdomains_off:Expected 0 (0) == > > > matches_log_signal(_metadata, self->audit_fd, child_data.parent_pid, > > > NULL) (-11) > > > > This error number means "EAGAIN 11 Resource temporarily unavailable", > > so it could be a temporary error. > > Yes, the test is flaky under pressure. > > > > > Can you reproduce this issue? Is it really dependent on my patch as > > blamed above? If so, does the selftest rely on the previous, incorrect > > order? > > I don't think it directly depends on your patch but it might be a side > effect. Anyway, I've been working on fixing this kind of issue and just > sent a fix: > https://lore.kernel.org/r/[email protected] Thanks, unfortunately I can't validate that it will fix the issue at hand. Thomas
