On Fri, May 15, 2020 at 12:18 PM Ondrej Mosnacek <omosnace@xxxxxxxxxx> wrote: > > On Fri, May 15, 2020 at 6:47 PM William Roberts > <bill.c.roberts@xxxxxxxxx> wrote: > > On Fri, May 15, 2020 at 11:41 AM Ondrej Mosnacek <omosnace@xxxxxxxxxx> wrote: > > > > > > On Fri, May 15, 2020 at 6:27 PM William Roberts > > > <bill.c.roberts@xxxxxxxxx> wrote: > > > > I am having an issue with the test suite, perhaps the error would be obvious > > > > to you or someone else > > > > > > > > Error: > > > > make[3]: Entering directory '/root/selinux-testsuite/tests/module_load' > > > > make[3]: *** /lib/modules/5.6.6-300.fc32.x86_64/build: No such file or > > > > directory. Stop. > > > > make[3]: Leaving directory '/root/selinux-testsuite/tests/module_load' > > > > make[2]: *** [Makefile:8: all] Error 2 > > > > make[2]: Leaving directory '/root/selinux-testsuite/tests/module_load' > > > > make[1]: *** [Makefile:141: all] Error 1 > > > > make[1]: Leaving directory '/root/selinux-testsuite/tests' > > > > make: *** [Makefile:8: test] Error 2 > > > > > > > > The module_load path exists: > > > > [root@demo tests]# ls /lib/modules/5.6.6-300.fc32.x86_64/ > > > > bls.conf modules.builtin modules.drm source > > > > build modules.builtin.alias.bin modules.modesetting symvers.gz > > > > config modules.builtin.bin modules.networking System.map > > > > kernel modules.builtin.modinfo modules.order updates > > > > modules.alias modules.dep modules.softdep vdso > > > > modules.alias.bin modules.dep.bin modules.symbols vmlinuz > > > > modules.block modules.devname modules.symbols.bin > > > > > > > > And build exists, but it's a file, is that right? > > > > [root@demo tests]# stat /lib/modules/5.6.6-300.fc32.x86_64/build > > > > File: /lib/modules/5.6.6-300.fc32.x86_64/build -> > > > > /usr/src/kernels/5.6.6-300.fc32.x86_64 > > > > Size: 38 Blocks: 0 IO Block: 4096 symbolic link > > > > Device: 801h/2049d Inode: 154128 Links: 1 > > > > Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) > > > > Context: system_u:object_r:modules_object_t:s0 > > > > Access: 2020-05-15 16:23:03.854826122 +0000 > > > > Modify: 2020-04-21 14:01:58.000000000 +0000 > > > > Change: 2020-04-22 22:30:37.051096556 +0000 > > > > Birth: - > > > > > > It is a symlink, as evident from the stat output above, which is > > > > very evident, how did I not notice that... (face palm) > > > > > normal. You probably just don't have the matching kernel-devel package > > > installed, so the target directory (/usr/src/...) doesn't exist. > > > > It seems installed: > > There is a subtle catch :) You need to have the exact version that > matches your $(uname -r). In your case it seems to be > 5.6.6-300.fc32.x86_64, while you probably only have the latest version > of kernel-devel (5.6.12-300.fc32.x86_64). Try: > > dnf install -y kernel-devel-$(uname -r) That actually worked as is and the test suite is running, a few things have failed, but another step in the right direction. > > Note that this may fail if the corresponding version is no longer in > the repos (5.6.12 >> 5.6.6, so it will probably fail in your case). In > that case you need to reboot the VM so that you run under the latest > installed kernel, for which you have kernel-devel. > > > full logs here: > > https://travis-ci.org/github/williamcroberts/selinux/builds/687514828 > > > > I ran this on my local VM in same error state: > > # dnf install -y kernel-devel > > Last metadata expiration check: 0:39:22 ago on Fri 15 May 2020 04:05:19 PM UTC. > > Package kernel-devel-5.6.12-300.fc32.x86_64 is already installed. > > Dependencies resolved. > > Nothing to do. > > Complete! > > > > Should we add this to the dnf command in the README?: > > https://github.com/SELinuxProject/selinux-testsuite > > -- > Ondrej Mosnacek <omosnace at redhat dot com> > Software Engineer, Security Technologies > Red Hat, Inc. >
