❌ FAIL: Test report for kernel 5.11.4-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.4-50.fc33
COPR build ID: 2060604
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
x86_64:
❌ 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?pre...
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:
x86_64:
Host 1:
❌ Boot test
⚡⚡⚡ ACPI table test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking: igmp conformance test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking ipsec: basic netns - transport
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: sanity smoke test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ i2c: i2cdetect sanity
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Firmware test suite
🚧 ⚡⚡⚡ jvm - jcstress tests
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ Networking cki netfilter test
🚧 ⚡⚡⚡ audit: audit testsuite test
Host 2:
❌ Boot test
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ CPU: Frequency Driver Test
🚧 ⚡⚡⚡ CPU: Idle Test
🚧 ⚡⚡⚡ xfstests - ext4
🚧 ⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ xfstests - nfsv4.2
🚧 ⚡⚡⚡ xfstests - cifsv3.11
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ power-management: cpupower/sanity test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: lvm device-mapper test
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng
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 ⏱.
3 years, 1 month
✅ PASS: Test report for kernel 5.11.4-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.4-50.fc33
COPR build ID: 2060604
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?pre...
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
✅ ACPI table test
✅ ACPI enabled test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Networking socket: fuzz
✅ Networking: igmp conformance test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Libkcapi AF_ALG test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ storage: SCSI VPD
✅ trace: ftrace/tracer
🚧 ✅ i2c: i2cdetect sanity
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ Firmware test suite
🚧 ✅ jvm - jcstress tests
🚧 ✅ Memory function: kaslr
🚧 ✅ Ethernet drivers sanity
🚧 ✅ Networking cki netfilter test
🚧 ❌ audit: audit testsuite test
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
✅ selinux-policy: serge-testsuite
✅ storage: software RAID testing
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: lvm device-mapper test
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng
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 ⏱.
3 years, 1 month
❌ FAIL: Test report for kernel 5.11.4-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.4-50.fc33
COPR build ID: 2060604
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
aarch64:
❌ 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?pre...
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
⚡⚡⚡ ACPI table test
⚡⚡⚡ ACPI enabled test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking: igmp conformance test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking ipsec: basic netns - transport
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ i2c: i2cdetect sanity
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Firmware test suite
🚧 ⚡⚡⚡ jvm - jcstress tests
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ Networking cki netfilter test
🚧 ⚡⚡⚡ audit: audit testsuite test
Host 2:
❌ Boot test
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ xfstests - ext4
🚧 ⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: lvm device-mapper test
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng
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 ⏱.
3 years, 1 month
[OS-BUILD PATCH] redhat: fix and rename fedora-configs and rh-configs
targets
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
redhat: fix and rename fedora-configs and rh-configs targets
Since the rename of all targets to dist-* targets, the specific config
targets for Fedora and RHEL do not work anymore: the makefile filters
only dist-% and distg-% targets, so it doesn't run against
redhat/Makefile and thus calling those targets do not work (as they
of course do not exist on the main kernel Makefile).
We have two approaches to this: change makefile to accept those old
config targets, or rename them so the current filter/makefile works.
I chose the latter approach with this change: fedora-configs target
is renamed to dist-fedora-configs, while rh-configs target is renamed
to dist-rhel-configs.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/redhat/Makefile b/redhat/Makefile
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -135,11 +135,11 @@ dist-configs: dist-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh "$(FLAVOR)" 1; \
./process_configs.sh $(PROCESS_CONFIGS_OPTS) $(PACKAGE_NAME) $(KVERSION)
-fedora-configs: FLAVOR = fedora
-fedora-configs: dist-configs
+dist-fedora-configs: FLAVOR = fedora
+dist-fedora-configs: dist-configs
-rh-configs: FLAVOR = rhel
-rh-configs: dist-configs
+dist-rhel-configs: FLAVOR = rhel
+dist-rhel-configs: dist-configs
dist-configs-check: dist-configs-prep
cd $(REDHAT)/configs; ./process_configs.sh $(PROCESS_CONFIGS_CHECK_OPTS) $(PACKAGE_NAME)
@@ -516,8 +516,8 @@ dist-full-help:
@echo ' dist-cross-<arch>-rpms - [x86_64 only] execute rpm builds for specified'
@echo ' <arch> using RHEL cross compiler.'
@echo ' See dist-cross-<arch>-build for the supported archs.'
- @echo ' rh-configs - build ELN configs'
- @echo ' fedora-configs - build Fedora configs'
+ @echo ' dist-rhel-configs - build ELN configs'
+ @echo ' dist-fedora-configs - build Fedora configs'
@echo ''
@echo 'kABI targets:'
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/953
3 years, 1 month
[OS-BUILD PATCH] Revert "mm/kmemleak: skip late_init if not skip
disable"
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
Revert "mm/kmemleak: skip late_init if not skip disable"
This reverts commit 24d8743613b2a6a585fc68cfe95078d9a3d5b389.
This patch never went upstream. The original issue is expected to
be fixed instead by commit 2abd839aa7e615f2bbc50c8ba7deb9e40d186768
("kmemleak: Do not corrupt the object_list during clean-up"), see
eg.: https://lkml.org/lkml/2019/10/8/742
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/mm/kmemleak.c b/mm/kmemleak.c
--- a/mm/kmemleak.c
+++ b/mm/kmemleak.c
@@ -1960,11 +1960,6 @@ void __init kmemleak_init(void)
*/
static int __init kmemleak_late_init(void)
{
- if (!kmemleak_skip_disable) {
- kmemleak_disable();
- return 0;
- }
-
kmemleak_initialized = 1;
debugfs_create_file("kmemleak", 0644, NULL, NULL, &kmemleak_fops);
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/949
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in arch/arm64
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in arch/arm64
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_CMDLINE_EXTEND:
The command-line arguments provided by the boot loader will be
appended to the default kernel command string.
Symbol: CMDLINE_EXTEND [=n]
Type : bool
Defined at arch/arm64/Kconfig:1859
Prompt: Extend bootloader kernel arguments
Depends on: <choice>
Location:
-> Boot options
-> Default kernel command string (CMDLINE [=console=ttyAMA0])
-> Kernel command line type (<choice> [=y])
---
CONFIG_CMDLINE_FROM_BOOTLOADER:
Uses the command-line options passed by the boot loader. If
the boot loader doesn't provide any, the default kernel command
string provided in CMDLINE will be used.
Symbol: CMDLINE_FROM_BOOTLOADER [=y]
Type : bool
Defined at arch/arm64/Kconfig:1852
Prompt: Use bootloader kernel arguments if available
Depends on: <choice>
Location:
-> Boot options
-> Default kernel command string (CMDLINE [=console=ttyAMA0])
-> Kernel command line type (<choice> [=y])
---
Cc: Mark Salter <msalter(a)redhat.com>
Cc: Mark Langsdorf <mlangsdo(a)redhat.com>
Cc: Jeremy Linton <jlinton(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_CMDLINE_EXTEND b/redhat/configs/common/generic/CONFIG_CMDLINE_EXTEND
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CMDLINE_EXTEND
@@ -0,0 +1 @@
+# CONFIG_CMDLINE_EXTEND is not set
diff a/redhat/configs/common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER b/redhat/configs/common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER
@@ -0,0 +1 @@
+CONFIG_CMDLINE_FROM_BOOTLOADER=y
diff a/redhat/configs/pending-common/generic/CONFIG_CMDLINE_EXTEND b/redhat/configs/pending-common/generic/CONFIG_CMDLINE_EXTEND
--- a/redhat/configs/pending-common/generic/CONFIG_CMDLINE_EXTEND
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_CMDLINE_EXTEND:
-#
-# The command-line arguments provided by the boot loader will be
-# appended to the default kernel command string.
-#
-# Symbol: CMDLINE_EXTEND [=n]
-# Type : bool
-# Defined at arch/arm64/Kconfig:1859
-# Prompt: Extend bootloader kernel arguments
-# Depends on: <choice>
-# Location:
-# -> Boot options
-# -> Default kernel command string (CMDLINE [=console=ttyAMA0])
-# -> Kernel command line type (<choice> [=y])
-#
-#
-#
-# CONFIG_CMDLINE_EXTEND is not set
diff a/redhat/configs/pending-common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER b/redhat/configs/pending-common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER
--- a/redhat/configs/pending-common/generic/CONFIG_CMDLINE_FROM_BOOTLOADER
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_CMDLINE_FROM_BOOTLOADER:
-#
-# Uses the command-line options passed by the boot loader. If
-# the boot loader doesn't provide any, the default kernel command
-# string provided in CMDLINE will be used.
-#
-# Symbol: CMDLINE_FROM_BOOTLOADER [=y]
-# Type : bool
-# Defined at arch/arm64/Kconfig:1852
-# Prompt: Use bootloader kernel arguments if available
-# Depends on: <choice>
-# Location:
-# -> Boot options
-# -> Default kernel command string (CMDLINE [=console=ttyAMA0])
-# -> Kernel command line type (<choice> [=y])
-#
-#
-#
-CONFIG_CMDLINE_FROM_BOOTLOADER=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/940
3 years, 1 month
✅ PASS: Test report for kernel 5.10.21-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.21-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=63296118
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?pre...
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
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: lvm device-mapper test
🚧 ✅ Storage: swraid mdadm raid_module test
🚧 ✅ stress: stress-ng
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 2:
✅ Boot test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ❌ Storage: lvm device-mapper test
🚧 ✅ Storage: swraid mdadm raid_module test
s390x:
Host 1:
✅ Boot test
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
🚧 ✅ stress: stress-ng
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
x86_64:
Host 1:
⚡ 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
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: lvm device-mapper test
🚧 ✅ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ stress: stress-ng
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
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 ⏱.
3 years, 1 month
[OS-BUILD PATCH] [redhat] Make CONFIG_CRYPTO_DEV_QAT_* configs
x86-only and
unify them
by Vladis Dronov (via Email Bridge)
From: Vladis Dronov <vdronov(a)redhat.com>
[redhat] Make CONFIG_CRYPTO_DEV_QAT_* configs x86-only and unify them
Intel has confirmed that QAT hardware is x86 only. Unify all the related
configs under redhat/configs/common/generic/x86/.
Signed-off-by: Vladis Dronov <vdronov(a)redhat.com>
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_CRYPTO_DEV_QAT_4XXX is not set
diff a/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_4XXX b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_4XXX
--- /dev/null
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_4XXX
@@ -0,0 +1 @@
+CONFIG_CRYPTO_DEV_QAT_4XXX=m
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C3XXX b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXX
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C3XXX
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXX
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C3XXXVF b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXXVF
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C3XXXVF
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXXVF
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C62X b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62X
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C62X
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62X
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C62XVF b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62XVF
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_C62XVF
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62XVF
diff a/redhat/configs/ark/generic/x86/x86_64/CONFIG_CRYPTO_DEV_QAT_DH895xCC b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCC
--- a/redhat/configs/ark/generic/x86/x86_64/CONFIG_CRYPTO_DEV_QAT_DH895xCC
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCC
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF
+++ b/redhat/configs/common/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_DEV_QAT_4XXX b/redhat/configs/fedora/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_CRYPTO_DEV_QAT_4XXX:
-#
-# Support for Intel(R) QuickAssist Technology QAT_4xxx
-# for accelerating crypto and compression workloads.
-#
-# To compile this as a module, choose M here: the module
-# will be called qat_4xxx.
-#
-# Symbol: CRYPTO_DEV_QAT_4XXX [=n]
-# Type : tristate
-# Defined at drivers/crypto/qat/Kconfig:49
-# Prompt: Support for Intel(R) QAT_4XXX
-# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && X86 [=y] && PCI [=y]
-# Location:
-# -> Cryptographic API (CRYPTO [=y])
-# -> Hardware crypto devices (CRYPTO_HW [=y])
-# Selects: CRYPTO_DEV_QAT [=m]
-#
-#
-#
-CONFIG_CRYPTO_DEV_QAT_4XXX=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXX b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXX
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXX
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_C3XXX=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXXVF b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXXVF
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C3XXXVF
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_C3XXXVF=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62X b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62X
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62X
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_C62X=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62XVF b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62XVF
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_C62XVF
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_C62XVF=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCC b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCC
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCC
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_DH895xCC=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_DEV_QAT_DH895xCCVF
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/948
3 years, 1 month