kernel November 2021

kernel@lists.fedoraproject.org

5 participants
53 discussions

[OS-BUILD PATCH] redhat/configs: unset KEXEC_SIG for s390x zfcpdump
by Coiby Xu (via Email Bridge) 30 Nov '21

30 Nov '21

From: Coiby Xu <coxu(a)redhat.com> redhat/configs: unset KEXEC_SIG for s390x zfcpdump Commit c58c0d126a4640e5a93287e8e321a1f4c7be2f8a ("redhat/configs: enable KEXEC_SIG for aarch64 RHEL") deleted this file by mistake. Although it doesn't make a difference since KEXEC_SIG requires CONFIG_MODULE_SIG_FORMAT, unset KEXEC_SIG to make kernel-ark consistent with RHEL8 and RHEL9. Fixes: commit c58c0d126a4640e5a93287e8e321a1f4c7be2f8a ("redhat/configs: enable KEXEC_SIG for aarch64 RHEL") Signed-off-by: Coiby Xu <coxu(a)redhat.com> diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG @@ -0,0 +1 @@ +# CONFIG_KEXEC_SIG is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1491

4 4

✅ PASS: Test report for kernel 5.15.5-100.fc34 (fedora-34)
by CKI Project 26 Nov '21

26 Nov '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.15.5-100.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=79272205 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 3: ✅ Boot test ✅ Reboot test 🚧 💥 Storage blktests - srp Host 4: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 5: ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 2: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 3: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp s390x: Host 1: ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 3: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 4: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon x86_64: Host 1: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ⚡⚡⚡ LTP - commands ⚡⚡⚡ LTP - containers ⚡⚡⚡ LTP - dio ⚡⚡⚡ LTP - fs ⚡⚡⚡ LTP - fsx ⚡⚡⚡ LTP - math ⚡⚡⚡ LTP - hugetlb ⚡⚡⚡ LTP - mm ⚡⚡⚡ LTP - nptl ⚡⚡⚡ LTP - pty ⚡⚡⚡ LTP - ipc ⚡⚡⚡ LTP - tracing ⚡⚡⚡ LTP: openposix test suite ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Ethernet drivers sanity 🚧 ⚡⚡⚡ xarray-idr-radixtree-test 🚧 ⚡⚡⚡ NFS Connectathon Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] redhat/configs: enable CONFIG_RD_ZSTD for rhel
by Tao Liu (via Email Bridge) 26 Nov '21

26 Nov '21

From: Tao Liu <ltao(a)redhat.com> redhat/configs: enable CONFIG_RD_ZSTD for rhel Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2020132 Upstream Status: RHEL-only Kdump will use ZSTD as the default method for initramfs compression. When creating kdump initramfs, if squash module is not introduced in dracut, the whole initramfs will be compressed into zstd format, thus kernel CONFIG_RD_ZSTD is needed. Signed-off-by: Tao Liu <ltao(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_RD_ZSTD b/redhat/configs/common/generic/CONFIG_RD_ZSTD index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_RD_ZSTD +++ b/redhat/configs/common/generic/CONFIG_RD_ZSTD @@ -1 +1 @@ -# CONFIG_RD_ZSTD is not set +CONFIG_RD_ZSTD=y diff --git a/redhat/configs/fedora/generic/CONFIG_RD_ZSTD b/redhat/configs/fedora/generic/CONFIG_RD_ZSTD deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/CONFIG_RD_ZSTD +++ /dev/null @@ -1 +0,0 @@ -CONFIG_RD_ZSTD=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1473

3 3

❌ FAIL: Test report for kernel 5.15.4-101.fc34 (fedora-34)
by CKI Project 25 Nov '21

25 Nov '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.15.4-101.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=79205839 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: s390x: ❌ LTP - syscalls aarch64: ❌ LTP - syscalls 💥 stress: stress-ng - os ppc64le: ❌ LTP - syscalls x86_64: ❌ LTP - syscalls All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 2: ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 Host 3: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 4: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 7: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 💥 stress: stress-ng - os ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 4: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 5: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp s390x: Host 1: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 2: ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 3: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp x86_64: Host 1: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

❌ FAIL: Test report for kernel 5.15.4-100.fc34 (fedora-34)
by CKI Project 23 Nov '21

23 Nov '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.15.4-100.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=79155455 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: s390x: ❌ LTP - cve ❌ LTP - syscalls ❌ LTP - containers ❌ Boot test aarch64: 💥 stress: stress-ng - os ❌ LTP - syscalls ppc64le: ❌ LTP - syscalls x86_64: ❌ LTP - syscalls All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 💥 stress: stress-ng - os Host 2: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 3: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 4: ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp ppc64le: Host 1: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 3: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 4: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon s390x: Host 1: ✅ Boot test ✅ Reboot test ❌ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ❌ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ❌ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 3: ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 4: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp x86_64: Host 1: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 4: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] kasan: test: Silence intentional read overflow warnings
by Justin M. Forbes (via Email Bridge) 21 Nov '21

21 Nov '21

From: Kees Cook <keescook(a)chromium.org> kasan: test: Silence intentional read overflow warnings As done in commit d73dad4eb5ad ("kasan: test: bypass __alloc_size checks") for __write_overflow warnings, also silence some more cases that trip the __read_overflow warnings seen in 5.16-rc1[1]: In file included from /kisskb/src/include/linux/string.h:253, from /kisskb/src/include/linux/bitmap.h:10, from /kisskb/src/include/linux/cpumask.h:12, from /kisskb/src/include/linux/mm_types_task.h:14, from /kisskb/src/include/linux/mm_types.h:5, from /kisskb/src/include/linux/page-flags.h:13, from /kisskb/src/arch/arm64/include/asm/mte.h:14, from /kisskb/src/arch/arm64/include/asm/pgtable.h:12, from /kisskb/src/include/linux/pgtable.h:6, from /kisskb/src/include/linux/kasan.h:29, from /kisskb/src/lib/test_kasan.c:10: In function 'memcmp', inlined from 'kasan_memcmp' at /kisskb/src/lib/test_kasan.c:897:2: /kisskb/src/include/linux/fortify-string.h:263:25: error: call to '__read_overflow' declared with attribute error: detected read beyond size of object (1st parameter) 263 | __read_overflow(); | ^~~~~~~~~~~~~~~~~ In function 'memchr', inlined from 'kasan_memchr' at /kisskb/src/lib/test_kasan.c:872:2: /kisskb/src/include/linux/fortify-string.h:277:17: error: call to '__read_overflow' declared with attribute error: detected read beyond size of object (1st parameter) 277 | __read_overflow(); | ^~~~~~~~~~~~~~~~~ [1] http://kisskb.ellerman.id.au/kisskb/buildresult/14660585/log/ Cc: Marco Elver <elver(a)google.com> Cc: Andrey Ryabinin <ryabinin.a.a(a)gmail.com> Cc: Alexander Potapenko <glider(a)google.com> Cc: Andrey Konovalov <andreyknvl(a)gmail.com> Cc: Dmitry Vyukov <dvyukov(a)google.com> Cc: kasan-dev(a)googlegroups.com Fixes: d73dad4eb5ad ("kasan: test: bypass __alloc_size checks") Signed-off-by: Kees Cook <keescook(a)chromium.org> Reviewed-by: Andrey Konovalov <andreyknvl(a)gmail.com> diff --git a/lib/test_kasan.c b/lib/test_kasan.c index blahblah..blahblah 100644 --- a/lib/test_kasan.c +++ b/lib/test_kasan.c @@ -869,6 +869,7 @@ static void kasan_memchr(struct kunit *test) ptr = kmalloc(size, GFP_KERNEL | __GFP_ZERO); KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ptr); + OPTIMIZER_HIDE_VAR(size); KUNIT_EXPECT_KASAN_FAIL(test, kasan_ptr_result = memchr(ptr, '1', size + 1)); @@ -894,6 +895,7 @@ static void kasan_memcmp(struct kunit *test) KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ptr); memset(arr, 0, sizeof(arr)); + OPTIMIZER_HIDE_VAR(size); KUNIT_EXPECT_KASAN_FAIL(test, kasan_int_result = memcmp(ptr, arr, size+1)); kfree(ptr); -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1501

1 1

❌ FAIL: Test report for kernel 5.14.20-200.fc34 (fedora-34)
by CKI Project 19 Nov '21

19 Nov '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.14.20-200.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=79040092 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: s390x: ❌ LTP - syscalls aarch64: 💥 stress: stress-ng - os ❌ LTP - syscalls ppc64le: ❌ LTP - syscalls x86_64: ❌ LTP - syscalls All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 💥 stress: stress-ng - os Host 3: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ Ethernet drivers sanity - mlx5 Host 5: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 6: ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 2: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp Host 4: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 5: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp s390x: Host 1: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp x86_64: Host 1: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 5: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ xfstests - nfsv4.2 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCHv2] kernel/rh_taint.c: Update to new messaging
by Prarit Bhargava (via Email Bridge) 19 Nov '21

19 Nov '21

From: Prarit Bhargava <prarit(a)redhat.com> kernel/rh_taint.c: Update to new messaging Bugzilla: https://bugzilla.redhat.com/2019377 Upstream Status: RHEL only Red Hat requires customer-facing messages to inform users that hardware and drivers are scheduled to be removed from support ie) disabled in the kernel. Hardware and drivers that are scheduled to be disabled in a future release fall into two categories: unmaintained and deprecated. Deprecated hardware and drivers continue to be fully maintained in the current release, but will be disabled in a future major release. Unmaintained hardware and drivers may receive security fixes and are also disabled in a future major release. The new messages have been agreed upon by the RHBU and RH Engineering. The changes include renaming rh_taint.c to rh_message.c and adding PCI device specific functions. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index blahblah..blahblah 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -752,7 +752,8 @@ static void rh_check_supported(void) pr_crit("Detected processor %s %s\n", boot_cpu_data.x86_vendor_id, boot_cpu_data.x86_model_id); - mark_hardware_unsupported("Processor"); + mark_hardware_unmaintained("x86 processor", "%s %s", boot_cpu_data.x86_vendor_id, + boot_cpu_data.x86_model_id); break; } diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c index blahblah..blahblah 100644 --- a/drivers/net/team/team.c +++ b/drivers/net/team/team.c @@ -3045,7 +3045,7 @@ static int __init team_module_init(void) if (err) goto err_nl_init; - mark_hardware_deprecated(DRV_NAME); + mark_driver_deprecated(DRV_NAME); return 0; diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c index blahblah..blahblah 100644 --- a/drivers/pci/pci-driver.c +++ b/drivers/pci/pci-driver.c @@ -296,33 +296,83 @@ static struct attribute *pci_drv_attrs[] = { }; ATTRIBUTE_GROUPS(pci_drv); +#if CONFIG_RHEL_DIFFERENCES /** - * pci_hw_vendor_status - Tell if a PCI device is supported by the HW vendor + * pci_hw_deprecated - Tell if a PCI device is deprecated * @ids: array of PCI device id structures to search in * @dev: the PCI device structure to match against * - * Used by a driver to check whether this device is in its list of unsupported + * Used by a driver to check whether this device is in its list of deprecated * devices. Returns the matching pci_device_id structure or %NULL if there is * no match. * * Reserved for Internal Red Hat use only. */ -const struct pci_device_id *pci_hw_vendor_status( - const struct pci_device_id *ids, +const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev) +{ + const struct pci_device_id *ret = pci_match_id(ids, dev); + + if (!ret) + return NULL; + + mark_hardware_deprecated(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); + return ret; +} +EXPORT_SYMBOL(pci_hw_deprecated); + +/** + * pci_hw_unmaintained - Tell if a PCI device is unmaintained + * @ids: array of PCI device id structures to search in + * @dev: the PCI device structure to match against + * + * Used by a driver to check whether this device is in its list of unmaintained + * devices. Returns the matching pci_device_id structure or %NULL if there is + * no match. + * + * Reserved for Internal Red Hat use only. + */ +const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, struct pci_dev *dev) { - char devinfo[64]; const struct pci_device_id *ret = pci_match_id(ids, dev); - if (ret) { - snprintf(devinfo, sizeof(devinfo), "%s %s", - dev_driver_string(&dev->dev), dev_name(&dev->dev)); - mark_hardware_deprecated(devinfo); - } + if (!ret) + return NULL; + mark_hardware_unmaintained(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); return ret; } -EXPORT_SYMBOL(pci_hw_vendor_status); +EXPORT_SYMBOL(pci_hw_unmaintained); + +/** + * pci_hw_disabled - Tell if a PCI device is disabled + * @ids: array of PCI device id structures to search in + * @dev: the PCI device structure to match against + * + * Used by a driver to check whether this device is in its list of disabled + * devices. Returns the matching pci_device_id structure or %NULL if there is + * no match. + * + * Reserved for Internal Red Hat use only. + */ +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev) +{ + const struct pci_device_id *ret = pci_match_id(ids, dev); + + if (!ret) + return NULL; + + mark_hardware_disabled(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); + return ret; +} +EXPORT_SYMBOL(pci_hw_disabled); + +#endif struct drv_dev_and_id { struct pci_driver *drv; diff --git a/include/linux/kernel.h b/include/linux/kernel.h index blahblah..blahblah 100644 --- a/include/linux/kernel.h +++ b/include/linux/kernel.h @@ -499,17 +499,19 @@ static inline void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) { } struct module; #ifdef CONFIG_RHEL_DIFFERENCES -void mark_hardware_unsupported(const char *msg); -void mark_hardware_deprecated(const char *msg); +void mark_hardware_unmaintained(const char *driver_name, char *fmt, ...); +void mark_driver_unmaintained(const char *driver_name); +void mark_hardware_deprecated(const char *driver_name, char *fmt, ...); +void mark_driver_deprecated(const char *driver_name); +void mark_hardware_disabled(const char *driver_name, char *fmt, ...); void mark_tech_preview(const char *msg, struct module *mod); -void mark_driver_unsupported(const char *name); -void mark_driver_deprecated(const char *name); #else -static inline void mark_hardware_unsupported(const char *msg) { } -static inline void mark_hardware_deprecated(const char *msg) { } +static inline void mark_hardware_unsupported(const char *driver_name, char *fmt, ...) { } +static inline void mark_driver_unmaintained(const char *driver_name) { } +static inline void mark_hardware_deprecated(const char *driver_name, char *fmt, ...) { } +static inline void mark_driver_deprecated(const char *driver_name) { } +static inline void mark_hardware_disabled(const char *driver_name, char *fmt, ...) { } static inline void mark_tech_preview(const char *msg, struct module *mod) { } -static inline void mark_driver_unsupported(const char *name) { } -static inline void mark_driver_deprecated(const char *name) { } #endif #endif diff --git a/include/linux/pci.h b/include/linux/pci.h index blahblah..blahblah 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -1478,10 +1478,22 @@ int pci_add_dynid(struct pci_driver *drv, unsigned long driver_data); const struct pci_device_id *pci_match_id(const struct pci_device_id *ids, struct pci_dev *dev); -/* Reserved for Internal Red Hat use only */ -const struct pci_device_id *pci_hw_vendor_status( - const struct pci_device_id *ids, + +#ifdef CONFIG_RHEL_DIFFERENCES +const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev); +const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, struct pci_dev *dev); +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev); +#else +static inline const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev) { return NULL; } +static inline const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, + struct pci_dev *dev) { return NULL; } +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev) {return NULL; } +#endif int pci_scan_bridge(struct pci_bus *bus, struct pci_dev *dev, int max, int pass); diff --git a/kernel/Makefile b/kernel/Makefile index blahblah..blahblah 100644 --- a/kernel/Makefile +++ b/kernel/Makefile @@ -12,7 +12,7 @@ obj-y = fork.o exec_domain.o panic.o \ notifier.o ksysfs.o cred.o reboot.o \ async.o range.o smpboot.o ucount.o regset.o -obj-$(CONFIG_RHEL_DIFFERENCES) += rh_taint.o +obj-$(CONFIG_RHEL_DIFFERENCES) += rh_messages.o obj-$(CONFIG_USERMODE_DRIVER) += usermode_driver.o obj-$(CONFIG_MODULES) += kmod.o obj-$(CONFIG_MULTIUSER) += groups.o diff --git a/kernel/rh_messages.c b/kernel/rh_messages.c new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/kernel/rh_messages.c @@ -0,0 +1,179 @@ +#include <linux/kernel.h> +#include <linux/module.h> + +#define DEV_DESC_LEN 256 +/* + * The following functions are used by Red Hat to indicate to users that + * hardware and drivers are unsupported, or have limited support in RHEL major + * and minor releases. These functions output loud warning messages to the end + * user and should be USED WITH CAUTION. + * + * Any use of these functions _MUST_ be documented in the RHEL Release Notes, + * and have approval of management. + * + * Generally, the process of disabling a driver or device in RHEL requires the + * driver or device to be marked as 'deprecated' in all existing releases, and + * then either 'unmaintained' or 'disabled' in a future release. + * + * In general, deprecated and unmaintained drivers continue to receive security + * related fixes until they are disabled. + */ + +/** + * mark_hardware_unmaintained() - Mark hardware as unmaintained. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that the device will no longer be tested on a routine + * basis and driver code associated with this device is no longer being updated. + * Red Hat may fix security-related and critical issues. Support for this device + * will be disabled in a future major release and users deploying this device + * should plan to replace the device in production systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_unmaintained(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Unmaintained hardware is detected: %s:%s\n", driver_name, + device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_unmaintained); + +/** + * mark_driver_unmaintained() - Mark a driver as unmaintained. + * @driver_name: driver name + * + * Called to notify users that a driver will no longer be tested on a routine + * basis and the driver code is no longer being updated. Red Hat may fix + * security-related and critical issues. Support for this driver will be + * disabled in a future major release, and users should replace any affected + * devices in production systems. + * + * This function should be used when a driver's usage cannot be tied to a + * specific hardware device. For example, a network bonding driver or a higher + * level storage layer driver that is no longer maintained upstream. + */ +void mark_driver_unmaintained(const char *driver_name) +{ + pr_crit("Warning: Unmaintained driver is detected: %s\n", driver_name); +} +EXPORT_SYMBOL(mark_driver_unmaintained); + +/** + * mark_hardware_deprecated() - Mark hardware as deprecated. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that support for the device is planned to be + * unmaintained in a future major release, and will eventually be disabled in a + * future major release. This device should not be used in new production + * environments and users should replace the device in production systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_deprecated(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Deprecated Hardware is detected: %s:%s will not be maintained in a future major release and may be disabled\n", + driver_name, device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_deprecated); + +/** + * mark_driver_deprecated() - Mark a driver as deprecated. + * @driver_name: driver name + * + * Called to notify users that support for this driver is planned to be + * unmaintained in a future major release, and will eventually be disabled in a + * future major release. This driver should not be used in new production + * environments and users should replace any affected devices in production + * systems. + * + * This function should be used when a driver's usage cannot be tied to a + * specific hardware device. For example, a network bonding driver or a higher + * level storage layer driver that is no longer maintained upstream. + */ +void mark_driver_deprecated(const char *driver_name) +{ + pr_crit("Warning: Deprecated Driver is detected: %s will not be maintained in a future major release and may be disabled\n", + driver_name); +} +EXPORT_SYMBOL(mark_driver_deprecated); + +/** + * mark_hardware_disabled() - Mark a driver as removed. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that a device's support has been completely disabled + * and no future support updates will occur. This device cannot be used in new + * production environments, and users must replace the device in production + * systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_disabled(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Disabled Hardware is detected: %s:%s is no longer enabled in this release.\n", + driver_name, device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_disabled); + +/** + * mark_tech_preview() - Mark driver or kernel subsystem as 'Tech Preview' + * @msg: Driver or kernel subsystem name + * + * Called to minimize the support status of a new driver. This does TAINT the + * kernel. Calling this function indicates that the driver or subsystem has + * had limited testing and is not marked for full support within this RHEL + * minor release. The next RHEL minor release may contain full support for + * this driver. Red Hat does not guarantee that bugs reported against this + * driver or subsystem will be resolved. + */ +void mark_tech_preview(const char *msg, struct module *mod) +{ + const char *str = NULL; + + if (msg) + str = msg; +#ifdef CONFIG_MODULES + else if (mod && mod->name) + str = mod->name; +#endif + + pr_warn("TECH PREVIEW: %s may not be fully supported.\n" + "Please review provided documentation for limitations.\n", + (str ? str : "kernel")); + add_taint(TAINT_AUX, LOCKDEP_STILL_OK); +#ifdef CONFIG_MODULES + if (mod) + mod->taints |= (1U << TAINT_AUX); +#endif +} +EXPORT_SYMBOL(mark_tech_preview); diff --git a/kernel/rh_taint.c b/kernel/rh_taint.c deleted file mode 100644 index blahblah..blahblah 0 --- a/kernel/rh_taint.c +++ /dev/null @@ -1,109 +0,0 @@ -#include <linux/kernel.h> -#include <linux/module.h> - -/* - * The following functions are used by Red Hat to indicate to users that - * hardware and drivers are unsupported, or have limited support in RHEL major - * and minor releases. These functions output loud warning messages to the end - * user and should be USED WITH CAUTION. - * - * Any use of these functions _MUST_ be documented in the RHEL Release Notes, - * and have approval of management. - */ - -/** - * mark_hardware_unsupported() - Mark hardware, class, or type as unsupported. - * @msg: Hardware name, class, or type - * - * Called to mark a device, class of devices, or types of devices as not having - * support in any RHEL minor release. This does not TAINT the kernel. Red Hat - * will not fix bugs against this hardware in this minor release. Red Hat may - * declare support in a future major or minor update release. This cannot be - * used to mark drivers unsupported. - */ -void mark_hardware_unsupported(const char *msg) -{ - /* Print one single message */ - pr_crit("Warning: %s - this hardware has not undergone testing by Red Hat and might not be certified. Please consult https://catalog.redhat.com for certified hardware.\n", msg); -} -EXPORT_SYMBOL(mark_hardware_unsupported); - -/** - * mark_hardware_deprecated() - Mark hardware, class, or type as deprecated. - * @msg: Hardware name, class, or type - * - * Called to minimize the support status of a previously supported device in - * a minor release. This does not TAINT the kernel. Marking hardware - * deprecated is usually done in conjunction with the hardware vendor. Future - * RHEL major releases may not include this driver. Driver updates and fixes - * for this device will be limited to critical issues in future minor releases. - */ -void mark_hardware_deprecated(const char *msg) -{ - pr_crit("Warning: %s - this hardware is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes for this device will be limited to critical issues. Please contact Red Hat Support or your device's hardware vendor for additional information.\n", msg); -} -EXPORT_SYMBOL(mark_hardware_deprecated); - -/** - * mark_tech_preview() - Mark driver or kernel subsystem as 'Tech Preview' - * @msg: Driver or kernel subsystem name - * - * Called to minimize the support status of a new driver. This does TAINT the - * kernel. Calling this function indicates that the driver or subsystem has - * had limited testing and is not marked for full support within this RHEL - * minor release. The next RHEL minor release may contain full support for - * this driver. Red Hat does not guarantee that bugs reported against this - * driver or subsystem will be resolved. - */ -void mark_tech_preview(const char *msg, struct module *mod) -{ - const char *str = NULL; - - if (msg) - str = msg; -#ifdef CONFIG_MODULES - else if (mod && mod->name) - str = mod->name; -#endif - - pr_warn("TECH PREVIEW: %s may not be fully supported.\n" - "Please review provided documentation for limitations.\n", - (str ? str : "kernel")); - add_taint(TAINT_AUX, LOCKDEP_STILL_OK); -#ifdef CONFIG_MODULES - if (mod) - mod->taints |= (1U << TAINT_AUX); -#endif -} -EXPORT_SYMBOL(mark_tech_preview); - -/** - * mark_driver_unsupported - drivers that we know we don't want to support - * @name: the name of the driver - * - * In some cases Red Hat has chosen to build a driver for internal QE - * use. Use this function to mark those drivers as unsupported for - * customers. - */ -void mark_driver_unsupported(const char *name) -{ - pr_crit("Warning: %s - This driver has not undergone sufficient testing by Red Hat for this release and therefore cannot be used in production systems.\n", - name ? name : "kernel"); -} -EXPORT_SYMBOL(mark_driver_unsupported); - -/** - * mark_driver_deprecated() - Mark drivers as deprecated. - * @name: the name of the driver - * - * Called to minimize the support status of a previously supported driver in - * a minor release. This does not TAINT the kernel. Future - * RHEL major releases may not include this driver. Driver updates and fixes - * will be limited to critical issues in future minor releases. - */ -void mark_driver_deprecated(const char *name) -{ - pr_crit("Warning: %s - this driver is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes will be limited to critical issues. Please contact Red Hat Support for additional information.\n", - name ? name : "kernel"); -} -EXPORT_SYMBOL(mark_driver_deprecated); -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1459

1 0

[OS-BUILD PATCH] kernel/rh_taint.c: Update to new messaging
by Prarit Bhargava (via Email Bridge) 19 Nov '21

19 Nov '21

From: Prarit Bhargava <prarit(a)redhat.com> kernel/rh_taint.c: Update to new messaging Bugzilla: https://bugzilla.redhat.com/2019377 Upstream Status: RHEL only Red Hat requires customer-facing messages to inform users that hardware and drivers are scheduled to be removed from support ie) disabled in the kernel. Hardware and drivers that are scheduled to be disabled in a future release fall into two categories: unmaintained and deprecated. Deprecated hardware and drivers continue to be fully maintained in the current release, but will be disabled in a future major release. Unmaintained hardware and drivers may receive security fixes and are also disabled in a future major release. The new messages have been agreed upon by the RHBU and RH Engineering. The changes include renaming rh_taint.c to rh_message.c and adding PCI device specific functions. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index blahblah..blahblah 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -752,7 +752,8 @@ static void rh_check_supported(void) pr_crit("Detected processor %s %s\n", boot_cpu_data.x86_vendor_id, boot_cpu_data.x86_model_id); - mark_hardware_unsupported("Processor"); + mark_hardware_unmaintained("x86 processor", "%s %s", boot_cpu_data.x86_vendor_id, + boot_cpu_data.x86_model_id); break; } diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c index blahblah..blahblah 100644 --- a/drivers/net/team/team.c +++ b/drivers/net/team/team.c @@ -3045,7 +3045,7 @@ static int __init team_module_init(void) if (err) goto err_nl_init; - mark_hardware_deprecated(DRV_NAME); + mark_driver_deprecated(DRV_NAME); return 0; diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c index blahblah..blahblah 100644 --- a/drivers/pci/pci-driver.c +++ b/drivers/pci/pci-driver.c @@ -296,33 +296,83 @@ static struct attribute *pci_drv_attrs[] = { }; ATTRIBUTE_GROUPS(pci_drv); +#if CONFIG_RHEL_DIFFERENCES /** - * pci_hw_vendor_status - Tell if a PCI device is supported by the HW vendor + * pci_hw_deprecated - Tell if a PCI device is deprecated * @ids: array of PCI device id structures to search in * @dev: the PCI device structure to match against * - * Used by a driver to check whether this device is in its list of unsupported + * Used by a driver to check whether this device is in its list of deprecated * devices. Returns the matching pci_device_id structure or %NULL if there is * no match. * * Reserved for Internal Red Hat use only. */ -const struct pci_device_id *pci_hw_vendor_status( - const struct pci_device_id *ids, +const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev) +{ + const struct pci_device_id *ret = pci_match_id(ids, dev); + + if (!ret) + return NULL; + + mark_hardware_deprecated(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); + return ret; +} +EXPORT_SYMBOL(pci_hw_deprecated); + +/** + * pci_hw_unmaintained - Tell if a PCI device is unmaintained + * @ids: array of PCI device id structures to search in + * @dev: the PCI device structure to match against + * + * Used by a driver to check whether this device is in its list of unmaintained + * devices. Returns the matching pci_device_id structure or %NULL if there is + * no match. + * + * Reserved for Internal Red Hat use only. + */ +const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, struct pci_dev *dev) { - char devinfo[64]; const struct pci_device_id *ret = pci_match_id(ids, dev); - if (ret) { - snprintf(devinfo, sizeof(devinfo), "%s %s", - dev_driver_string(&dev->dev), dev_name(&dev->dev)); - mark_hardware_deprecated(devinfo); - } + if (!ret) + return NULL; + mark_hardware_unmaintained(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); return ret; } -EXPORT_SYMBOL(pci_hw_vendor_status); +EXPORT_SYMBOL(pci_hw_unmaintained); + +/** + * pci_hw_disabled - Tell if a PCI device is disabled + * @ids: array of PCI device id structures to search in + * @dev: the PCI device structure to match against + * + * Used by a driver to check whether this device is in its list of disabled + * devices. Returns the matching pci_device_id structure or %NULL if there is + * no match. + * + * Reserved for Internal Red Hat use only. + */ +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev) +{ + const struct pci_device_id *ret = pci_match_id(ids, dev); + + if (!ret) + return NULL; + + mark_hardware_disabled(dev_driver_string(&dev->dev), "%04X:%04X @ %s", + dev->device, dev->vendor, pci_name(dev)); + return ret; +} +EXPORT_SYMBOL(pci_hw_disabled); + +#endif struct drv_dev_and_id { struct pci_driver *drv; diff --git a/include/linux/kernel.h b/include/linux/kernel.h index blahblah..blahblah 100644 --- a/include/linux/kernel.h +++ b/include/linux/kernel.h @@ -499,17 +499,19 @@ static inline void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) { } struct module; #ifdef CONFIG_RHEL_DIFFERENCES -void mark_hardware_unsupported(const char *msg); -void mark_hardware_deprecated(const char *msg); +void mark_hardware_unmaintained(const char *driver_name, char *fmt, ...); +void mark_driver_unmaintained(const char *driver_name); +void mark_hardware_deprecated(const char *driver_name, char *fmt, ...); +void mark_driver_deprecated(const char *driver_name); +void mark_hardware_disabled(const char *driver_name, char *fmt, ...); void mark_tech_preview(const char *msg, struct module *mod); -void mark_driver_unsupported(const char *name); -void mark_driver_deprecated(const char *name); #else -static inline void mark_hardware_unsupported(const char *msg) { } -static inline void mark_hardware_deprecated(const char *msg) { } +static inline void mark_hardware_unsupported(const char *driver_name, char *fmt, ...) { } +static inline void mark_driver_unmaintained(const char *driver_name) { } +static inline void mark_hardware_deprecated(const char *driver_name, char *fmt, ...) { } +static inline void mark_driver_deprecated(const char *driver_name) { } +static inline void mark_hardware_disabled(const char *driver_name, char *fmt, ...) { } static inline void mark_tech_preview(const char *msg, struct module *mod) { } -static inline void mark_driver_unsupported(const char *name) { } -static inline void mark_driver_deprecated(const char *name) { } #endif #endif diff --git a/include/linux/pci.h b/include/linux/pci.h index blahblah..blahblah 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -1478,10 +1478,22 @@ int pci_add_dynid(struct pci_driver *drv, unsigned long driver_data); const struct pci_device_id *pci_match_id(const struct pci_device_id *ids, struct pci_dev *dev); -/* Reserved for Internal Red Hat use only */ -const struct pci_device_id *pci_hw_vendor_status( - const struct pci_device_id *ids, + +#ifdef CONFIG_RHEL_DIFFERENCES +const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev); +const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, struct pci_dev *dev); +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev); +#else +static inline const struct pci_device_id *pci_hw_deprecated(const struct pci_device_id *ids, + struct pci_dev *dev) { return NULL; } +static inline const struct pci_device_id *pci_hw_unmaintained(const struct pci_device_id *ids, + struct pci_dev *dev) { return NULL; } +const struct pci_device_id *pci_hw_disabled(const struct pci_device_id *ids, + struct pci_dev *dev) {return NULL; } +#endif int pci_scan_bridge(struct pci_bus *bus, struct pci_dev *dev, int max, int pass); diff --git a/kernel/Makefile b/kernel/Makefile index blahblah..blahblah 100644 --- a/kernel/Makefile +++ b/kernel/Makefile @@ -12,7 +12,7 @@ obj-y = fork.o exec_domain.o panic.o \ notifier.o ksysfs.o cred.o reboot.o \ async.o range.o smpboot.o ucount.o regset.o -obj-$(CONFIG_RHEL_DIFFERENCES) += rh_taint.o +obj-$(CONFIG_RHEL_DIFFERENCES) += rh_messages.o obj-$(CONFIG_USERMODE_DRIVER) += usermode_driver.o obj-$(CONFIG_MODULES) += kmod.o obj-$(CONFIG_MULTIUSER) += groups.o diff --git a/kernel/rh_messages.c b/kernel/rh_messages.c new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/kernel/rh_messages.c @@ -0,0 +1,179 @@ +#include <linux/kernel.h> +#include <linux/module.h> + +#define DEV_DESC_LEN 256 +/* + * The following functions are used by Red Hat to indicate to users that + * hardware and drivers are unsupported, or have limited support in RHEL major + * and minor releases. These functions output loud warning messages to the end + * user and should be USED WITH CAUTION. + * + * Any use of these functions _MUST_ be documented in the RHEL Release Notes, + * and have approval of management. + * + * Generally, the process of disabling a driver or device in RHEL requires the + * driver or device to be marked as 'deprecated' in all existing releases, and + * then either 'unmaintained' or 'disabled' in a future release. + * + * In general, deprecated and unmaintained drivers continue to receive security + * related fixes until they are disabled. + */ + +/** + * mark_hardware_unmaintained() - Mark hardware as unmaintained. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that the device will no longer be tested on a routine + * basis and driver code associated with this device is no longer being updated. + * Red Hat may fix security-related and critical issues. Support for this device + * will be disabled in a future major release and users deploying this device + * should plan to replace the device in production systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_unmaintained(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Unmaintained hardware is detected: %s:%s\n", driver_name, + device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_unmaintained); + +/** + * mark_driver_unmaintained() - Mark a driver as unmaintained. + * @driver_name: driver name + * + * Called to notify users that a driver will no longer be tested on a routine + * basis and the driver code is no longer being updated. Red Hat may fix + * security-related and critical issues. Support for this driver will be + * disabled in a future major release, and users should replace any affected + * devices in production systems. + * + * This function should be used when a driver's usage cannot be tied to a + * specific hardware device. For example, a network bonding driver or a higher + * level storage layer driver that is no longer maintained upstream. + */ +void mark_driver_unmaintained(const char *driver_name) +{ + pr_crit("Warning: Unmaintained driver is detected: %s\n", driver_name); +} +EXPORT_SYMBOL(mark_driver_unmaintained); + +/** + * mark_hardware_deprecated() - Mark hardware as deprecated. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that support for the device is planned to be + * unmaintained in a future major release, and will eventually be disabled in a + * future major release. This device should not be used in new production + * environments and users should replace the device in production systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_deprecated(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Deprecated Hardware is detected: %s:%s will not be maintained a future major release and may be disabled\n", + driver_name, device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_deprecated); + +/** + * mark_driver_deprecated() - Mark a driver as deprecated. + * @driver_name: driver name + * + * Called to notify users that support for this driver is planned to be + * unmaintained in a future major release, and will eventually be disabled in a + * future major release. This driver should not be used in new production + * environments and users should replace any affected devices in production + * systems. + * + * This function should be used when a driver's usage cannot be tied to a + * specific hardware device. For example, a network bonding driver or a higher + * level storage layer driver that is no longer maintained upstream. + */ +void mark_driver_deprecated(const char *driver_name) +{ + pr_crit("Warning: Deprecated Driver is detected: %s will not be maintained in a future major release and may be disabled\n", + driver_name); +} +EXPORT_SYMBOL(mark_driver_deprecated); + +/** + * mark_hardware_disabled() - Mark a driver as removed. + * @driver_name: driver name + * @fmt: format for device description + * @...: args for device description + * + * Called to notify users that a device's support has been completely disabled + * and no future support updates will occur. This device cannot be used in new + * production environments, and users must replace the device in production + * systems. + * + * This function should be used when the driver's usage can be tied to a + * specific hardware device. For example, a network device driver loading on a + * specific device that is no longer maintained by the manufacturer. + */ +void mark_hardware_disabled(const char *driver_name, char *fmt, ...) +{ + char device_description[DEV_DESC_LEN]; + va_list args; + + va_start(args, fmt); + vsnprintf(device_description, DEV_DESC_LEN, fmt, args); + pr_crit("Warning: Disabled Hardware is detected: %s:%s is no longer enabled in this release.\n", + driver_name, device_description); + va_end(args); +} +EXPORT_SYMBOL(mark_hardware_disabled); + +/** + * mark_tech_preview() - Mark driver or kernel subsystem as 'Tech Preview' + * @msg: Driver or kernel subsystem name + * + * Called to minimize the support status of a new driver. This does TAINT the + * kernel. Calling this function indicates that the driver or subsystem has + * had limited testing and is not marked for full support within this RHEL + * minor release. The next RHEL minor release may contain full support for + * this driver. Red Hat does not guarantee that bugs reported against this + * driver or subsystem will be resolved. + */ +void mark_tech_preview(const char *msg, struct module *mod) +{ + const char *str = NULL; + + if (msg) + str = msg; +#ifdef CONFIG_MODULES + else if (mod && mod->name) + str = mod->name; +#endif + + pr_warn("TECH PREVIEW: %s may not be fully supported.\n" + "Please review provided documentation for limitations.\n", + (str ? str : "kernel")); + add_taint(TAINT_AUX, LOCKDEP_STILL_OK); +#ifdef CONFIG_MODULES + if (mod) + mod->taints |= (1U << TAINT_AUX); +#endif +} +EXPORT_SYMBOL(mark_tech_preview); diff --git a/kernel/rh_taint.c b/kernel/rh_taint.c deleted file mode 100644 index blahblah..blahblah 0 --- a/kernel/rh_taint.c +++ /dev/null @@ -1,109 +0,0 @@ -#include <linux/kernel.h> -#include <linux/module.h> - -/* - * The following functions are used by Red Hat to indicate to users that - * hardware and drivers are unsupported, or have limited support in RHEL major - * and minor releases. These functions output loud warning messages to the end - * user and should be USED WITH CAUTION. - * - * Any use of these functions _MUST_ be documented in the RHEL Release Notes, - * and have approval of management. - */ - -/** - * mark_hardware_unsupported() - Mark hardware, class, or type as unsupported. - * @msg: Hardware name, class, or type - * - * Called to mark a device, class of devices, or types of devices as not having - * support in any RHEL minor release. This does not TAINT the kernel. Red Hat - * will not fix bugs against this hardware in this minor release. Red Hat may - * declare support in a future major or minor update release. This cannot be - * used to mark drivers unsupported. - */ -void mark_hardware_unsupported(const char *msg) -{ - /* Print one single message */ - pr_crit("Warning: %s - this hardware has not undergone testing by Red Hat and might not be certified. Please consult https://catalog.redhat.com for certified hardware.\n", msg); -} -EXPORT_SYMBOL(mark_hardware_unsupported); - -/** - * mark_hardware_deprecated() - Mark hardware, class, or type as deprecated. - * @msg: Hardware name, class, or type - * - * Called to minimize the support status of a previously supported device in - * a minor release. This does not TAINT the kernel. Marking hardware - * deprecated is usually done in conjunction with the hardware vendor. Future - * RHEL major releases may not include this driver. Driver updates and fixes - * for this device will be limited to critical issues in future minor releases. - */ -void mark_hardware_deprecated(const char *msg) -{ - pr_crit("Warning: %s - this hardware is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes for this device will be limited to critical issues. Please contact Red Hat Support or your device's hardware vendor for additional information.\n", msg); -} -EXPORT_SYMBOL(mark_hardware_deprecated); - -/** - * mark_tech_preview() - Mark driver or kernel subsystem as 'Tech Preview' - * @msg: Driver or kernel subsystem name - * - * Called to minimize the support status of a new driver. This does TAINT the - * kernel. Calling this function indicates that the driver or subsystem has - * had limited testing and is not marked for full support within this RHEL - * minor release. The next RHEL minor release may contain full support for - * this driver. Red Hat does not guarantee that bugs reported against this - * driver or subsystem will be resolved. - */ -void mark_tech_preview(const char *msg, struct module *mod) -{ - const char *str = NULL; - - if (msg) - str = msg; -#ifdef CONFIG_MODULES - else if (mod && mod->name) - str = mod->name; -#endif - - pr_warn("TECH PREVIEW: %s may not be fully supported.\n" - "Please review provided documentation for limitations.\n", - (str ? str : "kernel")); - add_taint(TAINT_AUX, LOCKDEP_STILL_OK); -#ifdef CONFIG_MODULES - if (mod) - mod->taints |= (1U << TAINT_AUX); -#endif -} -EXPORT_SYMBOL(mark_tech_preview); - -/** - * mark_driver_unsupported - drivers that we know we don't want to support - * @name: the name of the driver - * - * In some cases Red Hat has chosen to build a driver for internal QE - * use. Use this function to mark those drivers as unsupported for - * customers. - */ -void mark_driver_unsupported(const char *name) -{ - pr_crit("Warning: %s - This driver has not undergone sufficient testing by Red Hat for this release and therefore cannot be used in production systems.\n", - name ? name : "kernel"); -} -EXPORT_SYMBOL(mark_driver_unsupported); - -/** - * mark_driver_deprecated() - Mark drivers as deprecated. - * @name: the name of the driver - * - * Called to minimize the support status of a previously supported driver in - * a minor release. This does not TAINT the kernel. Future - * RHEL major releases may not include this driver. Driver updates and fixes - * will be limited to critical issues in future minor releases. - */ -void mark_driver_deprecated(const char *name) -{ - pr_crit("Warning: %s - this driver is not recommended for new deployments. It continues to be supported in this RHEL release, but it is likely to be removed in the next major release. Driver updates and fixes will be limited to critical issues. Please contact Red Hat Support for additional information.\n", - name ? name : "kernel"); -} -EXPORT_SYMBOL(mark_driver_deprecated); -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1459

1 1

💥 PANICKED: Test report for kernel 5.14.19-200.fc34 (fedora-34)
by CKI Project 19 Nov '21

19 Nov '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.14.19-200.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=78991015 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: PANICKED One or more kernel tests failed: s390x: ❌ LTP - syscalls aarch64: 💥 stress: stress-ng - os ❌ LTP - syscalls ppc64le: ❌ LTP - syscalls x86_64: 💥 Boot test 💥 Boot test 💥 Boot test All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ storage: software RAID testing 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 💥 stress: stress-ng - os Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 3: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 4: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 5: ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 7: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 4: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp s390x: Host 1: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ❌ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ LTP: openposix test suite ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - srp Host 4: ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os x86_64: Host 1: 💥 Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP - cve ⚡⚡⚡ LTP - sched ⚡⚡⚡ LTP - syscalls ⚡⚡⚡ LTP - can ⚡⚡⚡ LTP - commands ⚡⚡⚡ LTP - containers ⚡⚡⚡ LTP - dio ⚡⚡⚡ LTP - fs ⚡⚡⚡ LTP - fsx ⚡⚡⚡ LTP - math ⚡⚡⚡ LTP - hugetlb ⚡⚡⚡ LTP - mm ⚡⚡⚡ LTP - nptl ⚡⚡⚡ LTP - pty ⚡⚡⚡ LTP - ipc ⚡⚡⚡ LTP - tracing ⚡⚡⚡ LTP: openposix test suite ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Ethernet drivers sanity 🚧 ⚡⚡⚡ xarray-idr-radixtree-test 🚧 ⚡⚡⚡ NFS Connectathon Host 4: 💥 Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp Host 5: 💥 Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP - cve ⚡⚡⚡ LTP - sched ⚡⚡⚡ LTP - syscalls ⚡⚡⚡ LTP - can ⚡⚡⚡ LTP - commands ⚡⚡⚡ LTP - containers ⚡⚡⚡ LTP - dio ⚡⚡⚡ LTP - fs ⚡⚡⚡ LTP - fsx ⚡⚡⚡ LTP - math ⚡⚡⚡ LTP - hugetlb ⚡⚡⚡ LTP - mm ⚡⚡⚡ LTP - nptl ⚡⚡⚡ LTP - pty ⚡⚡⚡ LTP - ipc ⚡⚡⚡ LTP - tracing ⚡⚡⚡ LTP: openposix test suite ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Ethernet drivers sanity 🚧 ⚡⚡⚡ xarray-idr-radixtree-test 🚧 ⚡⚡⚡ NFS Connectathon Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng - interrupt 🚧 ⚡⚡⚡ stress: stress-ng - cpu 🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache 🚧 ⚡⚡⚡ stress: stress-ng - memory 🚧 ⚡⚡⚡ stress: stress-ng - os Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel November 2021