❌ FAIL: Test report for kernel 5.18.2-200.fc36 (fedora-36)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.18.2-200.fc36
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=87940717
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
s390x:
❌ POSIX pjd-fstest suites
❌ storage: dm/common
❌ Storage: swraid mdadm raid_module test
❌ storage: targetcli basic
aarch64:
❌ Boot test
ppc64le:
❌ POSIX pjd-fstest suites
x86_64:
❌ POSIX pjd-fstest suites
❌ storage: dm/common
❌ Storage: swraid mdadm raid_module test
❌ storage: targetcli basic
❌ Reboot test
❌ xfstests - nfsv4.2
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:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
❌ Boot test
✅ IPMI driver test
✅ IPMItool loop stress test
✅ stress: stress-ng - interrupt
✅ stress: stress-ng - cpu
✅ stress: stress-ng - cpu-cache
✅ stress: stress-ng - memory
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage block - storage fio numa
✅ Reboot test
Host 2:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
⚡⚡⚡ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ ACPI table test
✅ ACPI enabled test
✅ i2c: i2cdetect sanity
✅ 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
⚡⚡⚡ POSIX pjd-fstest suites
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ jvm - jcstress tests
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ Networking: igmp conformance test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking cki netfilter test
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking tunnel: permtest
⚡⚡⚡ Networking ipsec: basic netns - transport
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Networking vnic: ipvlan/basic
⚡⚡⚡ Networking VRF: sanity
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ Storage: block zstd compression test
⚡⚡⚡ Storage: block zstd smoke test
⚡⚡⚡ storage: dm/common
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ lvm thinp stqe test
⚡⚡⚡ lvm snapper test
⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ Storage: swraid mdadm raid_module test
⚡⚡⚡ Storage: swraid scsi_raid
⚡⚡⚡ storage: targetcli basic
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Podman system test - as root
🚧 ⚡⚡⚡ Podman system test - as user
🚧 ⚡⚡⚡ NFS Connectathon
🚧 ⚡⚡⚡ Firmware test suite
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ lvm cache test
🚧 ⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ Reboot test
Host 5:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
Host 7:
⚡ 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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
ppc64le:
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ Reboot test
Host 2:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ IPMI driver test
✅ IPMItool loop stress test
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage block - storage fio numa
✅ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot 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
❌ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking cki netfilter test
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking tunnel: permtest
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Networking vnic: ipvlan/basic
⚡⚡⚡ Networking VRF: sanity
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ Storage: block zstd compression test
⚡⚡⚡ Storage: block zstd smoke test
⚡⚡⚡ storage: dm/common
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ lvm thinp stqe test
⚡⚡⚡ lvm snapper test
⚡⚡⚡ Storage: swraid mdadm raid_module test
⚡⚡⚡ Storage: swraid scsi_raid
⚡⚡⚡ storage: targetcli basic
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Podman system test - as root
🚧 ⚡⚡⚡ Podman system test - as user
🚧 ⚡⚡⚡ NFS Connectathon
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ lvm cache test
🚧 ⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ Reboot test
Host 4:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
Host 5:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
s390x:
Host 1:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot 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
❌ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking sctp-auth: sockopts test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking cki netfilter test
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking tunnel: permtest
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Networking vnic: ipvlan/basic
✅ Networking VRF: sanity
✅ Libkcapi AF_ALG test
✅ Storage: block zstd compression test
✅ Storage: block zstd smoke test
❌ storage: dm/common
✅ lvm thinp sanity
✅ lvm thinp stqe test
✅ lvm snapper test
❌ Storage: swraid mdadm raid_module test
✅ Storage: swraid scsi_raid
❌ storage: targetcli basic
✅ trace: ftrace/tracer
🚧 ❌ Podman system test - as root
🚧 ❌ Podman system test - as user
🚧 ✅ NFS Connectathon
🚧 ✅ Memory function: kaslr
🚧 ✅ lvm cache test
✅ Reboot 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp
⚡⚡⚡ Reboot test
Host 4:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ stress: stress-ng - interrupt
✅ stress: stress-ng - cpu
✅ stress: stress-ng - cpu-cache
✅ stress: stress-ng - memory
🚧 ✅ Storage blktests - nvme-tcp
✅ Reboot test
Host 5:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
Host 6:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
x86_64:
Host 1:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot 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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ CPU: Die Test
⚡⚡⚡ IPMI driver test
⚡⚡⚡ IPMItool loop stress test
⚡⚡⚡ stress: stress-ng - interrupt
⚡⚡⚡ stress: stress-ng - cpu
⚡⚡⚡ stress: stress-ng - cpu-cache
⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ CPU: Idle Test
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage block - storage fio numa
⚡⚡⚡ Reboot test
Host 3:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ ACPI table test
✅ i2c: i2cdetect sanity
✅ 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
❌ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ Networking: igmp conformance test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking cki netfilter test
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking tunnel: permtest
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Networking vnic: ipvlan/basic
✅ Networking VRF: sanity
✅ Libkcapi AF_ALG test
✅ pciutils: sanity smoke test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ Storage: block zstd compression test
✅ Storage: block zstd smoke test
❌ storage: dm/common
✅ lvm thinp sanity
✅ lvm thinp stqe test
✅ lvm snapper test
✅ storage: SCSI VPD
❌ Storage: swraid mdadm raid_module test
✅ Storage: swraid scsi_raid
❌ storage: targetcli basic
✅ trace: ftrace/tracer
🚧 ❌ Podman system test - as root
🚧 ❌ Podman system test - as user
🚧 ❌ NFS Connectathon
🚧 ✅ Firmware test suite
🚧 ❌ Memory function: kaslr
🚧 ✅ Usex - version 1.9-29
🚧 ✅ lvm cache test
🚧 ✅ storage: software RAID testing
❌ Reboot test
Host 4:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
Host 5:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
❌ xfstests - nfsv4.2
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - cifsv3.11
✅ Reboot test
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 year, 10 months
[OS-BUILD PATCHv2] redhat/configs/README: Update the README
by Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/configs/README: Update the README
The information in this file was a bit out-of-date and needed a refresh.
Update the README.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/configs/README b/redhat/configs/README
index blahblah..blahblah 100644
--- a/redhat/configs/README
+++ b/redhat/configs/README
@@ -1,63 +1,84 @@
-Red Hat Enterprise Linux Always Ready config option scheme
-------------------------------------------------------
+kernel-ark CONFIG option scheme
+-------------------------------
-Historically, the RHEL kernel is forked from a Fedora kernel.
-Today, the Always Ready Kernel (ARK) is constantly rebased as new kernel
-releases come out. New configuration options are reviewed and set
-with each release.
+The kernel-ark repository contains both Fedora and ark (aka "RHEL next")
+CONFIGS. This repository is constantly rebased as the upstream kernel releases
+new kernel version. New configuration options are reviewed and set with each
+release, typically during the -rc1 to -rc3 releases.
-The config options are split out into a hierarchical
-tree structure, with one file per config option at each level of the
-hierarchy. The config options are merged and properly layered according to
-the file "priority" in the same directory as this README to generate the
-final kernel-$VERSION-<arch>-<variant>.config files we need for building the
-actual kernels.
+The kernel-ark configs are broken out into ark, fedora, and common directories
+in which each directory provides a heirarchical layout of the configs starting
+with generic/CONFIG_* and debug/CONFIG_*, then generic/<arch>/CONFIG_* and
+generic/<arch>/<variant>/CONFIG_*, debug/<arch>/CONFIG_*, etc. Users should be
+aware that it may not necessarily be the case that architecture support is
+consistent between ark and fedora.
+
+The config options are merged and properly layered according to the priority.*
+files in the same directory as this README to generate the final
+kernel-$VERSION-<arch>-<variant>.config files we need for building the actual
+kernels. For example, the ark variant priorities are found in priority.rhel,
+and in the case of x86_64 architecture, the specific information required is,
+
+ORDER=common ark pending-ark custom-overrides
+
+and
+
+x86_64=generic:generic-x86:generic-x86-x86_64
+
+This indicates that for the x86_64 variant, the order that of inheritance would be:
+
+custom-overrides/generic/x86/x86_64 (highest override priority)
+custom-overrides/generic/x86
+custom-overrides/generic
+pending-ark/generic/x86/x86_64
+pending-ark/generic/x86
+pending-ark/generic
+ark/generic/x86/x86_64
+ark/generic/x86
+ark/generic
+common/generic/x86/x86_64
+common/generic/x86
+common/generic (lowest override priority)
+
+A text-based graphical representation of a specific CONFIG can be viewed
+by using the evaluate_configs utility in this directory.
+
+ ex) evaluate_configs -p priority.rhel -c CONFIG_PCI
+
+Directory Layout
+----------------
The configuration is broken down into several directories:
-ark - This contains all configuration options that have been fully
-reviewed by kernel developers and are suitable for inclusion at branch time.
-
-pending-common - This directory contains all configuration options that have
-not yet been fully reviewed for inclusion. Because of the rate at which
-kernel options come out, we can't guarantee everything has been reviewed
-by the time a build needs to happen. In the interest of letting the build
-proceed for other testing, configuration options are staged in the
-pending directory. It is expected that this directory will be empty
-at branch time.
-
-In each directory (ark etc.), we have generic/CONFIG_* and debug/CONFIG_*, then
-generic/<arch>/CONFIG_* and generic/<arch>/<variant>/CONFIG_*, as well as
-debug/<arch>/CONFIG_*. While this may seem overly complex compared with
-past RHEL kernel config setups at first glance, its actually quite
-straight-forward and should be less error-prone. There's no potential
-for configuration options getting out of order or conflicts when changing
-adjacent configuraiton options.
-
-pending-fedora - This directory contains configuration options that have not
-been reviewed by Fedora kernel maintainers. Since the Fedora kernel turns on
-more configuration options than ARK, there are often settings that are not set
-to default in pending-common. These settings are moved to the fedora/
-configuration directory after community review. Options are populated with
-"make FLAVOR=fedora dist-commit-configs".
-
-custom-overrides - This directory contains an empty set of the generic and debug
-arch-specific directory tree. Any config option set here is applied last and
-therefore will override anything set in the ark, fedora, or pending directories.
-This allows users to easily override a config option without altering the
-standard directories. Users can even maintain their own branch with a full set
-of custom configuration options that can be easily be rebased on top of
-os-build without worrying about conflicts.
-
-All the configuration options for each arch and variant can be found
-in the "priority" file.
-
-If you want to make a change that applies to all kernels, debug and
-non-debug alike, add a config option file under ark/generic/. If it should
-only apply to all debug kernels, add it under ark/debug/. Arch-specific
-options go under ark/generic/<arch>/ and so on. Each layer's individual config
-option files are concatenated together with all other options at the same
-level, then stacked atop the lower layers until reaching the highest
-precedence layer for the given config option.
-
-Send any questions, comments or concerns to rhkernel-list(a)redhat.com.
+ark - contains all configuration options that have been reviewed by kernel
+developers for the ark kernel.
+
+common - contains all configuration options that are common between the fedora
+and ark directories. In other words, these config settings apply to both
+fedora and ark.
+
+custom-overrides - contains an empty set of the generic and debug arch-specific
+directory tree. Any config option set here is applied last and therefore will
+override anything set in the ark, fedora, or pending directories. This feature
+was added to assist users executing custom builds to easily override a config
+option without altering the standard directories. Users can even maintain their
+own branch with a full set of custom configuration options that can be easily
+be rebased on top of os-build without worrying about conflicts.
+
+fedora - contains all configuration options that have been reviewed by kernel
+developers for the fedora kernel.
+
+pending-[ark][common][fedora] - These directories contain configuration options
+that have not yet been fully reviewed for inclusion for ark, fedora, and both
+(common) kernels. Due to the rate at which kernel options come out, the kernel
+maintainers cannot guarantee reviews of configs in these directories by the
+time a build occurs. In the interest of letting the build proceed for other
+testing, configuration options are staged in these pending directories.
+
+As pending-* configs are reviewed, they are moved into the matching non-pending
+directory (ie, pending-ark -> ark, etc.) and it is expected that these
+directories will be empty at branch time.
+
+Config files can be populated using the pending-* directories by using the
+"FLAVOR" Makefile variable; for example to build the fedora configs, users can
+execute "make FLAVOR=fedora dist-commit-configs".
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1841
1 year, 10 months
[OS-BUILD PATCH 0/0] fedora: some minor fixups and cleanups from my
backlog of
review
by pbrobinson (via Email Bridge)
From: pbrobinson on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1853
NOTE: Truncated patchset due to missing public @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the merge request to
retrigger sending the emails.
Enable a few missed arm drivers, and some other minor cleanups.
Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com>
---
redhat/configs/ark/generic/x86/x86_64/CONFIG_DWMAC_INTEL => redhat/configs/common/generic/x86/CONFIG_DWMAC_INTEL | 0
redhat/configs/fedora/generic/arm/aarch64/CONFIG_EXTCON_PTN5150 | 1 +
redhat/configs/fedora/generic/arm/aarch64/CONFIG_QCOM_GPI_DMA | 1 +
redhat/configs/fedora/generic/arm/aarch64/CONFIG_RTC_DRV_PM8XXX | 1 +
redhat/configs/fedora/generic/arm/CONFIG_DRM_PANEL_ILITEK_ILI9341 | 1 +
redhat/configs/fedora/generic/arm/CONFIG_KHADAS_MCU_FAN_THERMAL | 1 +
redhat/configs/fedora/generic/arm/CONFIG_MFD_KHADAS_MCU | 2 +-
redhat/configs/fedora/generic/CONFIG_QCOM_ADM => redhat/configs/fedora/generic/arm/CONFIG_QCOM_ADM | 0
redhat/configs/fedora/generic/arm/CONFIG_VIDEO_IMX290 | 1 -
redhat/configs/fedora/generic/arm/armv7/armv7/CONFIG_XILLYBUS_OF => redhat/configs/fedora/generic/arm/CONFIG_XILLYBUS_OF | 0
redhat/configs/fedora/generic/x86/CONFIG_DWMAC_INTEL | 1 -
redhat/configs/fedora/generic/x86/CONFIG_X86_PLATFORM_DRIVERS_DELL | 1 -
redhat/configs/fedora/generic/CONFIG_BATTERY_GOLDFISH | 1 -
redhat/configs/fedora/generic/CONFIG_DRM_GUD | 1 -
redhat/configs/fedora/generic/CONFIG_DWMAC_INTEL_PLAT | 2 +-
redhat/configs/fedora/generic/CONFIG_RTC_DRV_PM8XXX | 2 +-
16 files changed, 8 insertions(+), 8 deletions(-)
1 year, 10 months
[OS-BUILD PATCHv4] redhat/docs: Add a description of kernel naming
by Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/docs: Add a description of kernel naming
Add a file that describes how kernel NVRs are constructed.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/docs/index.rst b/redhat/docs/index.rst
index blahblah..blahblah 100644
--- a/redhat/docs/index.rst
+++ b/redhat/docs/index.rst
@@ -111,6 +111,7 @@ Contributor Guide
submitting-contributions
faq
makefile-changes
+ kernel-naming
Maintainer Guide
diff --git a/redhat/docs/kernel-naming.rst b/redhat/docs/kernel-naming.rst
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/docs/kernel-naming.rst
@@ -0,0 +1,44 @@
+.. _kernel-naming:
+
+=============
+Kernel Naming
+=============
+
+The kernel NVR looks like, for example,
+kernel-5.17.0-0.rc8.551acdc3c3d2.124.test.fc35. This string contains
+information about the upstream release, a unique build number, and information
+about the distribution the RPM was targeted for. An explanation of each of the
+fields and how the fields are used in the kernel NVR, is below.
+
+**PACKAGE_NAME**: This is the name of the package. By default this is
+'kernel', but a well-known variant is kernel-rt.
+
+**SPECKVERSION**: This is the VERSION variable defined in the top-level linux
+Makefile.
+
+**SPECKPATCHLEVEL**: This is the PATCHLEVEL variable defined in the top-level
+linux Makefile.
+
+**SPECKSUBLEVEL**: This is the SUBLEVEL variable defined in the top-level linux
+Makefile.
+
+**UPSTREAMBUILD**: This is a representation of the upstream build information.
+It includes the EXTRAVERSION variable (defined in the top-level Makefile) or
+'rc0' if the tree is based on an a specific upstream release. If the tree is
+not based on a specific "rc" release, this field also contains a git hash
+reference to the top of tree commit.
+
+**BUILD**: This is the RHEL_RELEASE variable defined in the top-level linux
+Makefile.rhelver.
+
+**LOCALVERSION**: By default, this variable is set to ".test". This value can
+be overriden by defining a string in redhat/localversion.
+
+**DIST**: This is the dist release suffix used in the package release, eg.
+.fc34 or .el9.
+
+The kernel name is constructed as
+
+$(PACKAGE_NAME)-$(SPECKVERSION).$(SPECKPATCHLEVEL).$(SPECKSUBLEVEL)-$(UPSTREAMBUILD)$(BUILD)$(LOCALVERSION)$(DIST)
+
+In general, the kernel follows the Fedora Naming Guidelines, `https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines <https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidel....
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1779
1 year, 10 months
❌ FAIL: Test report for kernel 5.18.1-200.fc36 (fedora-36)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.18.1-200.fc36
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=87836237
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
s390x:
❌ POSIX pjd-fstest suites
❌ storage: dm/common
❌ Storage: swraid mdadm raid_module test
❌ storage: targetcli basic
aarch64:
❌ LTP - syscalls
❌ POSIX pjd-fstest suites
❌ storage: dm/common
❌ Storage: swraid mdadm raid_module test
❌ storage: targetcli basic
x86_64:
❌ xfstests - nfsv4.2
❌ POSIX pjd-fstest suites
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:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ IPMI driver test
✅ IPMItool loop stress test
✅ stress: stress-ng - interrupt
✅ stress: stress-ng - cpu
✅ stress: stress-ng - cpu-cache
✅ stress: stress-ng - memory
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ❌ Storage block - storage fio numa
✅ Reboot test
Host 2:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
Host 3:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ ACPI table test
✅ ACPI enabled test
✅ i2c: i2cdetect sanity
✅ 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
❌ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ Networking: igmp conformance test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking cki netfilter test
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking tunnel: permtest
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Networking vnic: ipvlan/basic
✅ Libkcapi AF_ALG test
✅ pciutils: update pci ids test
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ Storage: block zstd compression test
✅ Storage: block zstd smoke test
❌ storage: dm/common
✅ lvm thinp sanity
✅ lvm thinp stqe test
✅ lvm snapper test
✅ storage: SCSI VPD
❌ Storage: swraid mdadm raid_module test
✅ Storage: swraid scsi_raid
❌ storage: targetcli basic
✅ trace: ftrace/tracer
🚧 ❌ Podman system test - as root
🚧 ⚡⚡⚡ Podman system test - as user
🚧 ⚡⚡⚡ NFS Connectathon
🚧 ⚡⚡⚡ Firmware test suite
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Networking VRF: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ lvm cache test
🚧 ⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
Host 7:
⚡ 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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
⚡⚡⚡ Reboot test
ppc64le:
Host 1:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot 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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot 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
⚡⚡⚡ POSIX pjd-fstest suites
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ jvm - jcstress tests
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking cki netfilter test
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking tunnel: permtest
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Networking vnic: ipvlan/basic
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ Storage: block zstd compression test
⚡⚡⚡ Storage: block zstd smoke test
⚡⚡⚡ storage: dm/common
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ lvm thinp stqe test
⚡⚡⚡ lvm snapper test
⚡⚡⚡ Storage: swraid mdadm raid_module test
⚡⚡⚡ Storage: swraid scsi_raid
⚡⚡⚡ storage: targetcli basic
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Podman system test - as root
🚧 ⚡⚡⚡ Podman system test - as user
🚧 ⚡⚡⚡ NFS Connectathon
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Networking VRF: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ lvm cache test
🚧 ⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ IPMI driver test
⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage block - storage fio numa
⚡⚡⚡ Reboot test
Host 4:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ IPMI driver test
⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage block - storage fio numa
⚡⚡⚡ Reboot test
Host 7:
⚡ 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
⚡⚡⚡ Reboot test
s390x:
Host 1:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot 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
❌ POSIX pjd-fstest suites
✅ Loopdev Sanity
✅ jvm - jcstress tests
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking sctp-auth: sockopts test
✅ Networking route: pmtu
✅ Networking route_func - local
✅ Networking route_func - forward
✅ Networking TCP: keepalive test
✅ Networking UDP: socket
✅ Networking cki netfilter test
✅ Networking tunnel: geneve basic test
✅ Networking tunnel: gre basic
✅ L2TP basic test
✅ Networking tunnel: vxlan basic
✅ Networking tunnel: permtest
✅ Networking ipsec: basic netns - transport
✅ Networking ipsec: basic netns - tunnel
✅ Networking vnic: ipvlan/basic
✅ Libkcapi AF_ALG test
✅ Storage: block zstd compression test
✅ Storage: block zstd smoke test
❌ storage: dm/common
✅ lvm thinp sanity
✅ lvm thinp stqe test
✅ lvm snapper test
❌ Storage: swraid mdadm raid_module test
✅ Storage: swraid scsi_raid
❌ storage: targetcli basic
✅ trace: ftrace/tracer
🚧 ❌ Podman system test - as root
🚧 ❌ Podman system test - as user
🚧 ✅ NFS Connectathon
🚧 ✅ Memory function: kaslr
🚧 ✅ Networking VRF: sanity
🚧 ✅ lvm cache test
✅ Reboot test
Host 2:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
Host 3:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ stress: stress-ng - interrupt
✅ stress: stress-ng - cpu
✅ stress: stress-ng - cpu-cache
✅ stress: stress-ng - memory
🚧 ✅ Storage blktests - nvme-tcp
✅ Reboot test
Host 4:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
🚧 ❌ Storage blktests - nvmeof-mp
✅ Reboot test
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.
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ CPU: Die Test
✅ IPMI driver test
✅ IPMItool loop stress test
✅ stress: stress-ng - interrupt
✅ stress: stress-ng - cpu
✅ stress: stress-ng - cpu-cache
✅ stress: stress-ng - memory
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage block - storage fio numa
⚡⚡⚡ Reboot test
Host 2:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ selinux-policy: serge-testsuite
✅ Reboot test
Host 3:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
❌ xfstests - nfsv4.2
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - cifsv3.11
✅ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp
⚡⚡⚡ Reboot test
Host 5:
🚧 ✅ SELinux Custom Module Setup
🚧 ✅ machineinfo
✅ Boot test
✅ ACPI table test
✅ i2c: i2cdetect sanity
✅ 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
❌ POSIX pjd-fstest suites
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ jvm - jcstress tests
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ Networking: igmp conformance test
⚡⚡⚡ Networking route: pmtu
⚡⚡⚡ Networking route_func - local
⚡⚡⚡ Networking route_func - forward
⚡⚡⚡ Networking TCP: keepalive test
⚡⚡⚡ Networking UDP: socket
⚡⚡⚡ Networking cki netfilter test
⚡⚡⚡ Networking tunnel: geneve basic test
⚡⚡⚡ Networking tunnel: gre basic
⚡⚡⚡ L2TP basic test
⚡⚡⚡ Networking tunnel: vxlan basic
⚡⚡⚡ Networking tunnel: permtest
⚡⚡⚡ Networking ipsec: basic netns - transport
⚡⚡⚡ Networking ipsec: basic netns - tunnel
⚡⚡⚡ Networking vnic: ipvlan/basic
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: sanity smoke test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ Storage: block zstd compression test
⚡⚡⚡ Storage: block zstd smoke test
⚡⚡⚡ storage: dm/common
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ lvm thinp stqe test
⚡⚡⚡ lvm snapper test
⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ Storage: swraid mdadm raid_module test
⚡⚡⚡ Storage: swraid scsi_raid
⚡⚡⚡ storage: targetcli basic
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Podman system test - as root
🚧 ⚡⚡⚡ Podman system test - as user
🚧 ⚡⚡⚡ NFS Connectathon
🚧 ⚡⚡⚡ Firmware test suite
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ Networking VRF: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ lvm cache test
🚧 ⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ Reboot test
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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp
⚡⚡⚡ Reboot test
Host 7:
⚡ 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.
🚧 ⚡⚡⚡ SELinux Custom Module Setup
🚧 ⚡⚡⚡ machineinfo
⚡⚡⚡ Boot test
⚡⚡⚡ CPU: Die Test
⚡⚡⚡ IPMI driver test
⚡⚡⚡ IPMItool loop stress test
⚡⚡⚡ stress: stress-ng - interrupt
⚡⚡⚡ stress: stress-ng - cpu
⚡⚡⚡ stress: stress-ng - cpu-cache
⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ CPU: Idle Test
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage block - storage fio numa
⚡⚡⚡ Reboot test
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 year, 10 months
[OS-BUILD PATCH] redhat/docs: Add a description of kernel naming
by Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/docs: Add a description of kernel naming
Add a file that describes how kernel NVRs are constructed.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/docs/index.rst b/redhat/docs/index.rst
index blahblah..blahblah 100644
--- a/redhat/docs/index.rst
+++ b/redhat/docs/index.rst
@@ -111,6 +111,7 @@ Contributor Guide
submitting-contributions
faq
makefile-changes
+ kernel-naming
Maintainer Guide
diff --git a/redhat/docs/kernel-naming.rst b/redhat/docs/kernel-naming.rst
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/docs/kernel-naming.rst
@@ -0,0 +1,44 @@
+.. _kernel-naming:
+
+=============
+Kernel Naming
+=============
+
+The kernel NVR looks like, for example,
+kernel-5.17.0-0.rc8.551acdc3c3d2.124.test.fc35. This string contains
+information about the upstream release, a unique build number, and information
+about the distribution the RPM was targeted for. An explanation of each of the
+fields and how the fields are used in the kernel NVR, is below.
+
+**PACKAGE_NAME**: This is the name of the package. By default this is
+'kernel', but a well-known variant is kernel-rt.
+
+**SPECKVERSION**: This is the VERSION variable defined in the top-level linux
+Makefile.
+
+**SPECKPATCHLEVEL**: This is the PATCHLEVEL variable defined in the top-level
+linux Makefile.
+
+**SUBLEVEL**: This is the SUBLEVEL variable defined in the top-level linux
+Makefile.
+
+**UPSTREAMBUILD**: This is a representation of the upstream build information.
+It includes the EXTRAVERSION variable (defined in the top-level Makefile) or
+'rc0' if the tree is based on an a specific upstream release. If the tree is
+not based on a specific "rc" release, this field also contains a git hash
+reference to the top of tree commit.
+
+**BUILD**: This is the RHEL_RELEASE variable defined in the top-level linux
+Makefile.rhelver.
+
+**LOCALVERSION**: By default, this variable is set to ".test". This value can
+be overriden by defining a string in redhat/localversion.
+
+**DIST**: This is the dist release suffix used in the package release, eg.
+.fc34 or .el9.
+
+The kernel name is constructed as
+
+$(PACKAGE_NAME)-$(SPECKVERSION).$(SPECKPATCHLEVEL).$(SPECKSUBLEVEL)-$(UPSTREAMBUILD)$(BUILD)$(LOCALVERSION)$(DIST)
+
+In general, the kernel follows the Fedora Naming Guidelines, `https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines <https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidel....
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1779
1 year, 10 months
[OS-BUILD PATCH] Explicitly turn off CONFIG_KASAN_INLINE for ppc
by Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Explicitly turn off CONFIG_KASAN_INLINE for ppc
While upstream commit 41b7a347 made us turn on KASAN_OUTLINE for ppc
because the depends for KASAN_INLINE are no longer met, those config
options are part of a "one or the other" Choice menu. Having both
enabled seems to make the Kbuild choke. We need to also explicitly
disable KASAN_INLINE
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff --git a/redhat/configs/pending-ark/debug/powerpc/CONFIG_KASAN_INLINE b/redhat/configs/ark/debug/powerpc/CONFIG_KASAN_INLINE
rename from redhat/configs/pending-ark/debug/powerpc/CONFIG_KASAN_INLINE
rename to redhat/configs/ark/debug/powerpc/CONFIG_KASAN_INLINE
index blahblah..blahblah 100644
--- a/redhat/configs/pending-ark/debug/powerpc/CONFIG_KASAN_INLINE
+++ b/redhat/configs/ark/debug/powerpc/CONFIG_KASAN_INLINE
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1842
1 year, 10 months
[OS-BUILD PATCH] RHMAINTAINERS: Update for June 3 2022
by Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava <prarit(a)redhat.com>
RHMAINTAINERS: Update for June 3 2022
Update RHMAINTAINERS to latest.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
index blahblah..blahblah 100644
--- a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
+++ b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
@@ -833,6 +833,7 @@ DISTRIBUTED LOCK MANAGER (DLM)
M: Alexander Aring <aahringo(a)redhat.com>
R: David Teigland <teigland(a)redhat.com>
R: Bob Peterson <rpeterso(a)redhat.com>
+R: Andreas Gruenbacher <agruenba(a)redhat.com>
S: Supported
F: fs/dlm/
@@ -1352,6 +1353,7 @@ M: Prarit Bhargava <prarit(a)redhat.com>
S: Supported
F: kernel/*.[ch]
X: kernel/audit*
+X: kernel/bpf/
X: kernel/crash_*.c
X: kernel/futex.c
X: kernel/kexec*
@@ -1895,6 +1897,16 @@ F: include/linux/if_team.h
F: include/uapi/linux/if_team.h
I: net
+NETWORKING [TUNTAP]
+M: Jason Wang <jasowang(a)redhat.com>
+S: Supported
+F: drivers/net/tap.c
+F: drivers/net/tun.c
+F: include/linux/if_tap.h
+F: include/linux/if_tun.h
+F: include/uapi/linux/if_tun.h
+I: net
+
NETXEN (1/10) GbE SUPPORT
M: Manish Chopra <mchopra(a)redhat.com>
M: Tony Camuso <tcamuso(a)redhat.com>
@@ -1929,6 +1941,7 @@ R: Ivan Vecera <ivecera(a)redhat.com>
R: Íñigo Huguet <ihuguet(a)redhat.com>
R: Jonathan Toppins <jtoppins(a)redhat.com>
R: Josef Oskera <joskera(a)redhat.com>
+R: Izabela Bakollari <ibakolla(a)redhat.com>
S: Supported
F: drivers/net/ethernet/
F: drivers/infiniband/
@@ -2346,6 +2359,7 @@ R: Juri Lelli <jlelli(a)redhat.com>
R: Luis Claudio Goncalves <lgoncalv(a)redhat.com>
R: Nico Pache <npache(a)redhat.com>
R: Oleg Nesterov <onestero(a)redhat.com>
+R: Valentin Schneider <vschneid(a)redhat.com>
S: Supported
F: kernel/sched/
F: include/linux/sched/
@@ -2819,6 +2833,7 @@ M: Dean Nelson <dnelson(a)redhat.com>
R: David Arcari <darcari(a)redhat.com>
R: Prarit Bhargava <prarit(a)redhat.com>
S: Supported
+F: arch/x86/include/asm/fpu/
F: arch/x86/kernel/fpu/
XDP (eXpress Data Path)
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1844
1 year, 10 months
[OS-BUILD PATCH] Change CRYPTO_CHACHA_S390 from m to y
by Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Change CRYPTO_CHACHA_S390 from m to y
Upstream commit 349d03ffd5f6 changed CRYPTO_CHACHA_S390 to select
CRYPTO_LIB_CHACHA_GENERIC which we already have as built-in. To avoid
mismatches, we need to move CRYPTO_CHACHA_S390 from module to built-in.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff --git a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA_S390 b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA_S390
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA_S390
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CHACHA_S390=y
diff --git a/redhat/configs/common/generic/s390x/CONFIG_CRYPTO_CHACHA_S390 b/redhat/configs/common/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
index blahblah..blahblah 100644
--- a/redhat/configs/common/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
+++ b/redhat/configs/common/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
@@ -1 +1 @@
-CONFIG_CRYPTO_CHACHA_S390=m
+CONFIG_CRYPTO_CHACHA_S390=y
diff --git a/redhat/configs/fedora/generic/s390x/CONFIG_CRYPTO_CHACHA_S390 b/redhat/configs/fedora/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/fedora/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CHACHA_S390=y
diff --git a/redhat/configs/pending-ark/generic/s390x/CONFIG_CRYPTO_CHACHA_S390 b/redhat/configs/pending-ark/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-ark/generic/s390x/CONFIG_CRYPTO_CHACHA_S390
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CHACHA_S390=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1834
1 year, 10 months
