January 2022 - kernel - Fedora Mailing-Lists

[OS-BUILD PATCH] Add gcc-c++ to BuildRequires

by GitLab Bridge on behalf of jmflinuxtx

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> This is required for some of the gcc plugins. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- redhat/kernel.spec.template | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index 5941924711d4..c8ee1f82c494 100755 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -501,7 +501,7 @@ Requires: kernel-modules-uname-r = %{KVERREL}%{?variant} # BuildRequires: kmod, patch, bash, tar, git-core BuildRequires: bzip2, xz, findutils, gzip, m4, perl-interpreter, perl-Carp, perl-devel, perl-generators, make, diffutils, gawk -BuildRequires: gcc, binutils, redhat-rpm-config, hmaccalc, bison, flex +BuildRequires: gcc, binutils, redhat-rpm-config, hmaccalc, bison, flex, gcc-c++ BuildRequires: net-tools, hostname, bc, elfutils-devel BuildRequires: dwarves BuildRequires: python3-devel -- GitLab

5 months, 1 week

4
3
0 / 0

[OS-BUILD PATCHv3] Enable KUNIT tests for redhat kernel-modules-internal

by Nico Pache (via Email Bridge)

From: Nico Pache <npache(a)redhat.com> Enable KUNIT tests for redhat kernel-modules-internal This commit will enable KUNIT tests to be compiled as modules and packaged into the kernel-modules-internal package. Signed-off-by: Nico Pache <npache(a)redhat.com> diff --git a/redhat/configs/common/debug/CONFIG_KASAN_KUNIT_TEST b/redhat/configs/common/debug/CONFIG_KASAN_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/debug/CONFIG_KASAN_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_KASAN_KUNIT_TEST=m diff --git a/redhat/configs/common/debug/CONFIG_TEST_LIST_SORT b/redhat/configs/common/debug/CONFIG_TEST_LIST_SORT index blahblah..blahblah 100644 --- a/redhat/configs/common/debug/CONFIG_TEST_LIST_SORT +++ b/redhat/configs/common/debug/CONFIG_TEST_LIST_SORT @@ -1 +1 @@ -CONFIG_TEST_LIST_SORT=y +CONFIG_TEST_LIST_SORT=m diff --git a/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT b/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT @@ -0,0 +1 @@ +# CONFIG_BITFIELD_KUNIT is not set diff --git a/redhat/configs/common/generic/CONFIG_BITS_TEST b/redhat/configs/common/generic/CONFIG_BITS_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_BITS_TEST @@ -0,0 +1 @@ +# CONFIG_BITS_TEST is not set diff --git a/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST @@ -0,0 +1 @@ +# CONFIG_CMDLINE_KUNIT_TEST is not set diff --git a/redhat/configs/common/generic/CONFIG_EXT4_KUNIT_TESTS b/redhat/configs/common/generic/CONFIG_EXT4_KUNIT_TESTS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_EXT4_KUNIT_TESTS @@ -0,0 +1 @@ +CONFIG_EXT4_KUNIT_TESTS=m diff --git a/redhat/configs/common/generic/CONFIG_FAT_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_FAT_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_FAT_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_FAT_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_KFENCE_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_KFENCE_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KFENCE_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_KFENCE_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_KUNIT b/redhat/configs/common/generic/CONFIG_KUNIT index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_KUNIT +++ b/redhat/configs/common/generic/CONFIG_KUNIT @@ -1 +1 @@ -# CONFIG_KUNIT is not set +CONFIG_KUNIT=m diff --git a/redhat/configs/common/generic/CONFIG_KUNIT_ALL_TESTS b/redhat/configs/common/generic/CONFIG_KUNIT_ALL_TESTS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KUNIT_ALL_TESTS @@ -0,0 +1 @@ +CONFIG_KUNIT_ALL_TESTS=m diff --git a/redhat/configs/common/generic/CONFIG_KUNIT_DEBUGFS b/redhat/configs/common/generic/CONFIG_KUNIT_DEBUGFS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KUNIT_DEBUGFS @@ -0,0 +1 @@ +CONFIG_KUNIT_DEBUGFS=y diff --git a/redhat/configs/common/generic/CONFIG_KUNIT_EXAMPLE_TEST b/redhat/configs/common/generic/CONFIG_KUNIT_EXAMPLE_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KUNIT_EXAMPLE_TEST @@ -0,0 +1 @@ +CONFIG_KUNIT_EXAMPLE_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST b/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST @@ -0,0 +1 @@ +# CONFIG_LINEAR_RANGES_TEST is not set diff --git a/redhat/configs/common/generic/CONFIG_LIST_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_LIST_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_LIST_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_LIST_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_MPTCP_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TESTS b/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TESTS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MPTCP_KUNIT_TESTS @@ -0,0 +1 @@ +CONFIG_MPTCP_KUNIT_TESTS=m diff --git a/redhat/configs/common/generic/CONFIG_RATIONAL_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_RATIONAL_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RATIONAL_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_RATIONAL_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_RESOURCE_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_RESOURCE_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RESOURCE_KUNIT_TEST @@ -0,0 +1 @@ +# CONFIG_RESOURCE_KUNIT_TEST is not set diff --git a/redhat/configs/common/generic/CONFIG_RTC_LIB_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_RTC_LIB_KUNIT_TEST new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RTC_LIB_KUNIT_TEST @@ -0,0 +1 @@ +CONFIG_RTC_LIB_KUNIT_TEST=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1422

9 months, 3 weeks

5
7
0 / 0

[OS-BUILD PATCH] Workaround for gcc12 compile issues in ubcmd-util.h

by Justin M. Forbes (via Email Bridge)

From: Justin M. Forbes <jforbes(a)fedoraproject.org> Workaround for gcc12 compile issues in ubcmd-util.h While upstream has made no move around this and I am not positive that this is the "proper" fix for upstream, it does get us building again for several arches. This is being added as "include in release" until upstream weighs in so that at least ark-latest builds for many architectures. There are still issues with gcc12 and armv7. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> diff --git a/tools/lib/subcmd/subcmd-util.h b/tools/lib/subcmd/subcmd-util.h index blahblah..blahblah 100644 --- a/tools/lib/subcmd/subcmd-util.h +++ b/tools/lib/subcmd/subcmd-util.h @@ -49,13 +49,12 @@ static NORETURN inline void die(const char *err, ...) static inline void *xrealloc(void *ptr, size_t size) { - void *ret = realloc(ptr, size); - if (!ret && !size) - ret = realloc(ptr, 1); + void *ret; + if (!size) + size = 1; + ret = realloc(ptr, size); if (!ret) { ret = realloc(ptr, size); - if (!ret && !size) - ret = realloc(ptr, 1); if (!ret) die("Out of memory, realloc failed"); } -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1594

1 year, 3 months

3
2
0 / 0

[OS-BUILD PATCHv2] kernel.spec: Add glibc-static build requirement

by Prarit Bhargava (via Email Bridge)

From: Prarit Bhargava <prarit(a)redhat.com> kernel.spec: Add glibc-static build requirement CKI and brew builds resulted in two different values for CONFIG_CC_CAN_LINK_STATIC. In CKI CONFIG_CC_CAN_LINK_STATIC=y while in brew CONFIG_CC_CAN_LINK_STATIC was not defined. This occurs because glibc-static is installed on the CKI build containers and was not installed in brew. In order to guarantee consistency across build systems add a build requirement for the glibc-static package. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index blahblah..blahblah 100755 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -585,6 +585,8 @@ BuildRequires: net-tools, hostname, bc, elfutils-devel BuildRequires: dwarves BuildRequires: python3-devel BuildRequires: gcc-plugin-devel +# required for CONFIG_CC_CAN_LINK_STATIC=y +BuildRequires: glibc-static %ifnarch %{nobuildarches} noarch BuildRequires: bpftool %endif -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1538

1 year, 3 months

7
13
0 / 0

[OS-BUILD PATCHv5] Enable iSER on s390x

by Stefan Schulze Frielinghaus (via Email Bridge)

From: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com> Enable iSER on s390x Tested: by IBM Upstream Status: RHEL only Signed-off-by: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com> diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_INFINIBAND_ISER is not set diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_INFINIBAND_ISERT is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1536

1 year, 3 months

3
4
0 / 0

[OS-BUILD PATCHv2] [redhat] virtio: enable virtio-mem on x86-64 as tech-preview

by David Hildenbrand (via Email Bridge)

From: David Hildenbrand <david(a)redhat.com> [redhat] virtio: enable virtio-mem on x86-64 as tech-preview Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2014492 Let's enable CONFIG_VIRTIO_MEM=m on x86-64 in RHEL 9. As it will be tech-preview, properly taint the kernel as soon as we're initializing the driver for an actual device in a !kdump environment where we might actually hot(un)plug memory when instructed by the hypervisor. We won't be tainting in a kdump kernel where the sole purpose is to check if a given PFN is actually part of a plugged virtio-mem device and can be dumped safely. Signed-off-by: David Hildenbrand <david(a)redhat.com> diff --git a/drivers/virtio/virtio_mem.c b/drivers/virtio/virtio_mem.c index blahblah..blahblah 100644 --- a/drivers/virtio/virtio_mem.c +++ b/drivers/virtio/virtio_mem.c @@ -2754,6 +2754,19 @@ static int virtio_mem_probe(struct virtio_device *vdev) /* trigger a config update to start processing the requested_size */ if (!vm->in_kdump) { +#ifdef CONFIG_RHEL_DIFFERENCES + static bool printed; + + /* + * virtio-mem, and especially its memory hot(un)plug + * functionality, is tech-preview. + */ + if (!printed) { + printed = true; + mark_tech_preview("virtio_mem", THIS_MODULE); + } +#endif /* CONFIG_RHEL_DIFFERENCES */ + atomic_set(&vm->config_changed, 1); queue_work(system_freezable_wq, &vm->wq); } diff --git a/redhat/configs/common/generic/x86/x86_64/CONFIG_VIRTIO_MEM b/redhat/configs/common/generic/x86/x86_64/CONFIG_VIRTIO_MEM index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/x86/x86_64/CONFIG_VIRTIO_MEM +++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_VIRTIO_MEM @@ -1 +1 @@ -# CONFIG_VIRTIO_MEM is not set +CONFIG_VIRTIO_MEM=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VIRTIO_MEM b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VIRTIO_MEM deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VIRTIO_MEM +++ /dev/null @@ -1 +0,0 @@ -CONFIG_VIRTIO_MEM=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1535

1 year, 3 months

2
4
0 / 0

[OS-BUILD PATCH 0/18] Forward port rh_kabi.h macros

by Prarit Bhargava (via Email Bridge)

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1530 Upstream Status: RHEL only Forward port rh_kabi.h macros. Signed-off-by: Čestmír Kalina <ckalina(a)redhat.com> Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> --- include/linux/rh_kabi.h | 436 ++++++++++++++++++++++++++++++++++++------------ 1 files changed, 327 insertions(+), 109 deletions(-)

1 year, 3 months

2
20
0 / 0

[OS-BUILD PATCH 0/5] [redhat] enable CONFIG_CMA on aarch64 in ARK as tech-preview

by David Hildenbrand (via Email Bridge)

From: David Hildenbrand on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1592 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2043141 Upstream: RHEL only The above bugzilla is for RHEL9/CS9 and I'll send a MR soon that performs the same changes to CS9. Enable CONFIG_CMA on aarch64 in ARK as we already have in fedora. We did the same change for x86-64 just recently. Move the relevant configs from redhat/configs/fedora to redhat/configs/common. While in tech-preview, we'll require a manual configuration of cma on the kernel command line -- we will default to "cma=0". Once e.g., "cma=64M" has been specified, cma_activate_area() will call mark_tech_preview("CMA"), essentially tainting the kernel. Once no longer in tech-preview, we can enable CMA as default by e.g., similarly defaulting to "cma=64M". The real change is preceded by some cleanups around CMA configs. Signed-off-by: David Hildenbrand <david(a)redhat.com> --- redhat/configs/ark/generic/arm/CONFIG_CMA_SIZE_MBYTES | 1 + redhat/configs/fedora/generic/arm/CONFIG_CMA => redhat/configs/common/generic/arm/CONFIG_CMA | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_ALIGNMENT => redhat/configs/common/generic/arm/CONFIG_CMA_ALIGNMENT | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_SIZE_SEL_MAX => redhat/configs/common/generic/arm/CONFIG_CMA_SIZE_SEL_MAX | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_SIZE_SEL_MBYTES => redhat/configs/common/generic/arm/CONFIG_CMA_SIZE_SEL_MBYTES | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_SIZE_SEL_MIN => redhat/configs/common/generic/arm/CONFIG_CMA_SIZE_SEL_MIN | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_SIZE_SEL_PERCENTAGE => redhat/configs/common/generic/arm/CONFIG_CMA_SIZE_SEL_PERCENTAGE | 0 redhat/configs/fedora/generic/arm/CONFIG_DMA_CMA => redhat/configs/common/generic/arm/CONFIG_DMA_CMA | 0 redhat/configs/common/generic/powerpc/CONFIG_CMA_AREAS | 1 - redhat/configs/common/generic/powerpc/CONFIG_CMA_DEBUG | 1 - redhat/configs/common/generic/powerpc/CONFIG_CMA_DEBUGFS | 1 - redhat/configs/common/generic/s390x/CONFIG_CMA_AREAS | 1 - redhat/configs/common/generic/s390x/CONFIG_CMA_DEBUG | 1 - redhat/configs/common/generic/s390x/CONFIG_CMA_DEBUGFS | 1 - redhat/configs/common/generic/x86/x86_64/CONFIG_CMA_AREAS | 1 - redhat/configs/common/generic/x86/x86_64/CONFIG_CMA_DEBUG | 1 - redhat/configs/common/generic/x86/x86_64/CONFIG_CMA_DEBUGFS | 1 - redhat/configs/ark/generic/CONFIG_CMA_AREAS => redhat/configs/common/generic/CONFIG_CMA_AREAS | 0 redhat/configs/ark/generic/CONFIG_CMA_DEBUG => redhat/configs/common/generic/CONFIG_CMA_DEBUG | 0 redhat/configs/ark/generic/CONFIG_CMA_DEBUGFS => redhat/configs/common/generic/CONFIG_CMA_DEBUGFS | 0 redhat/configs/fedora/generic/arm/CONFIG_CMA_AREAS | 1 - redhat/configs/fedora/generic/arm/CONFIG_CMA_DEBUG | 1 - redhat/configs/fedora/generic/CONFIG_CMA_SYSFS | 1 - 23 files changed, 1 insertions(+), 12 deletions(-)

1 year, 3 months

3
10
0 / 0

✅ PASS: Test report for kernel 5.16.4-200.fc35 (fedora-35)

by CKI Project

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.16.4-200.fc35 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=82107890 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: ⚡ 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 ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ Ethernet drivers sanity - mlx5 Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ 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 block - storage fio numa 🚧 ✅ 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. 🚧 ✅ SELinux Custom Module Setup ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 5: 🚧 ✅ SELinux Custom Module Setup ✅ 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 🚧 ✅ NFS Connectathon Host 6: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 ppc64le: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ 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 block - storage fio numa 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ 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 🚧 ✅ NFS Connectathon Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ 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 block - storage fio numa 🚧 ✅ 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 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ 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 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, 3 months

1
0
0 / 0

❌ FAIL: Test report for kernel 5.15.18-200.fc35 (fedora-35)

by CKI Project

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.15.18-200.fc35 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=82103024 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: ❌ LTP: openposix test suite 💥 Storage blktests - srp 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 ✅ 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 block - storage fio numa 🚧 ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ 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 🚧 ✅ NFS Connectathon Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 5: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 ppc64le: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ 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 block - storage fio numa 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ❌ Storage blktests - nvmeof-mp s390x: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ 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 🚧 ✅ NFS Connectathon Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ 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 block - storage fio numa 🚧 ✅ 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 2: 🚧 ✅ SELinux Custom Module Setup ✅ 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: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 4: 🚧 ✅ SELinux Custom Module Setup ✅ 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 year, 3 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel January 2022