Created attachment 1568001[details]
Output of runscript.sh (Fedora Test Week Kernel 5.1).
1. Please describe the problem:
Test script failed.
2. What is the Version-Release number of the kernel:
5.1
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Not tested.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
- Create a VM with QEMU/KVM (10GB storage VirtIO, qcow2; RAM 2 GB)
- Install kerneltest-5.1.iso (Fedora 31 rawhide)
- run runscript.sh in /liveuser/kerneltest/
Date: Mo 13. Mai 14:48:36 CEST 2019
Test set: default
Kernel: 5.1.1-300.fc30.x86_64
Release: Fedora release 31 (Rawhide)
Result: FAIL
Failed Tests: ./default/cachedrop
Warned Tests: None
============================================================
Starting test ./default/paxtest
Starting test ./default/cachedrop
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 1,21365 s, 86,4 MB/s
TestError: Can't free dentries and inodes
453028 440296
Could not run tests
Starting test ./default/mq-memory-corruption
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Test PASSED
Starting test ./default/libhugetlbfs
Starting test ./default/timer-overhead
cc timer-test.o -o timer-test
Starting test ./default/memfd
memfd_test.c: In function ‘mfd_assert_get_seals’:
memfd_test.c:67:6: warning: implicit declaration of function ‘fcntl’ [-Wimplicit-function-declaration]
67 | r = fcntl(fd, F_GET_SEALS);
| ^~~~~
memfd_test.c: In function ‘mfd_assert_open’:
memfd_test.c:190:6: warning: implicit declaration of function ‘open’; did you mean ‘popen’? [-Wimplicit-function-declaration]
190 | r = open(buf, flags, mode);
| ^~~~
| popen
memfd_test.c: In function ‘mfd_assert_write’:
memfd_test.c:315:6: warning: implicit declaration of function ‘fallocate’; did you mean ‘alloca’? [-Wimplicit-function-declaration]
315 | r = fallocate(fd,
| ^~~~~~~~~
| alloca
memfd: CREATE
memfd: BASIC
memfd: SEAL-WRITE
memfd: SEAL-SHRINK
memfd: SEAL-GROW
memfd: SEAL-RESIZE
memfd: SHARE-DUP
memfd: SHARE-MMAP
memfd: SHARE-OPEN
memfd: SHARE-FORK
memfd: SHARE-DUP (shared file-table)
memfd: SHARE-MMAP (shared file-table)
memfd: SHARE-OPEN (shared file-table)
memfd: SHARE-FORK (shared file-table)
memfd: DONE
Starting test ./default/sysfs-perms
Starting test ./default/selinux-dac-controls
Starting test ./default/posix_timers
Testing posix timers. False negative may happen on CPU execution
based timers if other threads run on the CPU...
Check itimer virtual... [OK]
Check itimer prof... [OK]
Check itimer real... [OK]
Check timer_create() per thread... [OK]
Check timer_create() per process... [OK]
Starting test ./default/modsign
Successfully loaded signed module
Successfully loaded unsigned module
Starting test ./default/stack-randomness
Starting test ./default/insert_leap_second
Setting time to speed up testing
Running for 1 iterations. Press ctrl-c to stop
Setting time to Tue May 14 01:59:50 2019
Scheduling leap second for Tue May 14 02:00:00 2019
Tue May 14 01:59:57 2019 + 285 us (37) TIME_INS
Tue May 14 01:59:57 2019 + 512465 us (37) TIME_INS
Tue May 14 01:59:58 2019 + 13529 us (37) TIME_INS
Tue May 14 01:59:58 2019 + 513676 us (37) TIME_INS
Tue May 14 01:59:59 2019 + 13766 us (37) TIME_INS
Tue May 14 01:59:59 2019 + 513883 us (37) TIME_INS
Tue May 14 01:59:59 2019 + 18597 us (38) TIME_OOP
Tue May 14 01:59:59 2019 + 518702 us (38) TIME_OOP
Tue May 14 02:00:00 2019 + 18940 us (38) TIME_WAIT
Tue May 14 02:00:00 2019 + 519023 us (38) TIME_WAIT
Tue May 14 02:00:01 2019 + 19129 us (38) TIME_WAIT
Tue May 14 02:00:01 2019 + 519230 us (38) TIME_WAIT
Tue May 14 02:00:02 2019 + 19323 us (38) TIME_WAIT
Leap complete
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
yes.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
no.
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
See attachment.