kernel February 2022

kernel@lists.fedoraproject.org

12 participants
78 discussions

[OS-BUILD PATCH 0/0] Add Partner Supported taint flag
by Alice Mitchell (via Email Bridge) 07 Feb '22

07 Feb '22

From: Alice Mitchell on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1603 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. This is to add a new kernel taint flag that indicates that this is a Partner Supported GPL module and not directly Supported by Red Hat, as per the policy document for partner Supported upstream kernel modules as linked from the bugzilla. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2038999 Upstream Status: RHEL only Signed-off-by: Alice Mitchell <ajmitchell(a)redhat.com> --- fs/afs/main.c | 1 + include/linux/panic.h | 2 +- kernel/panic.c | 2 +- kernel/rh_messages.c | 30 ++++++++++++++++++++++++++++++ 4 files changed, 33 insertions(+), 2 deletions(-)

2 1

✅ PASS: Test report for kernel 5.16.7-200.fc35 (fedora-35)
by CKI Project 07 Feb '22

07 Feb '22

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.16.7-200.fc35 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=82470433 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp 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 ✅ 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 5: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 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 ⚡⚡⚡ 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 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: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp x86_64: Host 1: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 2: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 3: 🚧 ✅ 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 4: 🚧 ✅ 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 Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

💥 PANICKED: Test report for kernel 5.16.6-200.fc35 (fedora-35)
by CKI Project 06 Feb '22

06 Feb '22

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.16.6-200.fc35 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=82420958 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: PANICKED One or more kernel tests failed: aarch64: 💥 stress: stress-ng - os 💥 Boot test All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: 🚧 ✅ 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 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 ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ Ethernet drivers sanity - mlx5 Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp Host 4: 🚧 ✅ 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 5: 🚧 ✅ SELinux Custom Module Setup 💥 Boot test ✅ Reboot test 🚧 ✅ Storage blktests - srp Host 6: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test ✅ Ethernet drivers sanity - mlx5 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 ⚡⚡⚡ 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: ⚡ 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 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 ⚡⚡⚡ 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: swraid mdadm raid_module test 🚧 ❌ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ stress: stress-ng - interrupt 🚧 ✅ stress: stress-ng - cpu 🚧 ✅ stress: stress-ng - cpu-cache 🚧 ✅ stress: stress-ng - memory 🚧 ✅ stress: stress-ng - os Host 3: 🚧 ✅ SELinux Custom Module Setup ✅ Boot test ✅ Reboot test 🚧 ✅ Storage blktests - nvmeof-mp x86_64: Host 1: 🚧 ✅ 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 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 ⚡⚡⚡ 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 ✅ 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 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 ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test 🚧 ⚡⚡⚡ Storage blktests - srp Host 6: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. 🚧 ⚡⚡⚡ 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 0

[OS-BUILD PATCHv6] Enable iSER on s390x
by Stefan Schulze Frielinghaus (via Email Bridge) 04 Feb '22

04 Feb '22

From: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com> Enable iSER on s390x Since the required hardware is available to our users, having iSER available as an option for our users seems appropriate. 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 1

[OS-BUILD PATCHv7] Makefile: Check PKGRELEASE size on dist-brew targets
by Prarit Bhargava (via Email Bridge) 03 Feb '22

03 Feb '22

From: Prarit Bhargava <prarit(a)redhat.com> Makefile: Check PKGRELEASE size on dist-brew targets The Red Hat brew system is a build system used internally within Red Hat which is similar to the externally available koji build system. One of the architectures of a brew build is 's390x+zfcpdump'. This arch using the default of localversion 'test' always causes the rpm build error: "5.17.0-0.rc0.20220114gitfb3b0673b7d5.65.test.el9_b.s390x+zfcpdump" exceeds 64 characters make: *** [Makefile:1257: include/generated/utsrelease.h] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.tMkhuG (%build) The 64 character limit is a size limit on UTSRELEASE and cannot be dynamically changed so the only other option is to reduce the package release (PKGRELEASE) string in length. Removing the date field and the string 'git' results in a string that is shorter by 11 characters, with a minimal loss in information. This option should not be set for the dist-git target so explicitly set PREBUILD_GIT_ONLY to zero on the dist-git and dist-git-test targets. Add an option, PREBUILD_GIT_ONLY, to shorten the PREBUILD variable which is used in the PKGRELEASE string. Add a check for the size of PKGRELEASE and return a pre-build error if PKGRELEASE is greater than 35 characters. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/redhat/Makefile b/redhat/Makefile index blahblah..blahblah 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -390,10 +390,19 @@ dist-koji : BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS) distg-brew: BUILD_FLAGS ?= $(BREW_FLAGS) $(TEST_FLAGS) distg-koji: BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS) -dist-brew dist-koji: dist-%: dist-srpm +dist-vr-check: + @# builds may include a s390x+zfcpdump arch build. UTS_RELEASE can only have a + @# version-release string with max 64 chars. The version-release for s390x+zfcpdump + @# is 29 characters, leaving a maximum of 35 characters for PKGRELEASE. + @if [ $$(echo -n $(PKGRELEASE) | wc -c) -gt 35 ]; then \ + echo "PKGRELEASE ($(PKGRELEASE)) is too long. Use a shorter localversion (currently $(BUILDID))"; \ + exit 1; \ + fi + +dist-brew dist-koji: dist-%: dist-vr-check dist-srpm $* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) $(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm $(OUTPUT_FILE) -distg-brew distg-koji: distg-%: +distg-brew distg-koji: distg-%: dist-vr-check $* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) "$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)" .PHONY: $(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec diff --git a/redhat/Makefile.common b/redhat/Makefile.common index blahblah..blahblah 100644 --- a/redhat/Makefile.common +++ b/redhat/Makefile.common @@ -75,9 +75,18 @@ ifeq ($(SNAPSHOT),1) PREBUILD:=0$(KEXTRAVERSION). RPMKPATCHLEVEL:=$(shell expr $(RPMKPATCHLEVEL) + 1) endif - # Obtain the date that HEAD was committed (not the snapshot commit). - HEAD_DATE:=$(shell $(GIT) show -s --format=%cd --date=format:%Y%m%d $(HEAD)) - PREBUILD:=$(PREBUILD)$(HEAD_DATE)git$(MARKER). + ifneq ($(filter $(MAKECMDGOALS),dist-git-test dist-git),) + PREBUILD_GIT_ONLY ?= 0 + else + PREBUILD_GIT_ONLY ?= 1 + endif + ifeq ($(PREBUILD_GIT_ONLY),1) + PREBUILD:=$(PREBUILD)$(MARKER). + else + # Obtain the date that HEAD was committed (not the snapshot commit). + HEAD_DATE:=$(shell $(GIT) show -s --format=%cd --date=format:%Y%m%d $(HEAD)) + PREBUILD:=$(PREBUILD)$(HEAD_DATE)git$(MARKER). + endif UPSTREAM_TARBALL_NAME:=$(patsubst v%,%,$(_TAG)) endif -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1579

3 4

[OS-BUILD PATCHv3] kernel.spec: Add glibc-static build requirement
by Prarit Bhargava (via Email Bridge) 03 Feb '22

03 Feb '22

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 environments 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,9 @@ BuildRequires: net-tools, hostname, bc, elfutils-devel BuildRequires: dwarves BuildRequires: python3-devel BuildRequires: gcc-plugin-devel +# glibc-static is required for a consistent build environment (specifically +# 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 1

[OS-BUILD PATCHv2] kernel.spec: Add glibc-static build requirement
by Prarit Bhargava (via Email Bridge) 03 Feb '22

03 Feb '22

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

7 13

[OS-BUILD PATCHv5] Enable iSER on s390x
by Stefan Schulze Frielinghaus (via Email Bridge) 03 Feb '22

03 Feb '22

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

3 4

[OS-BUILD PATCH] Enable KUNIT tests for testing
by Nico Pache (via Email Bridge) 03 Feb '22

03 Feb '22

From: Nico Pache <npache(a)redhat.com> Enable KUNIT tests for testing Some tests were accidently disabled: BITFIELD,CMDLINE,LINEAR_RANGES. Enable these tests, and add all the missing tests into the modules-internal package. Signed-off-by: Nico Pache <npache(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT b/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT +++ b/redhat/configs/common/generic/CONFIG_BITFIELD_KUNIT @@ -1 +1 @@ -# CONFIG_BITFIELD_KUNIT is not set +CONFIG_BITFIELD_KUNIT=m diff --git a/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST b/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST +++ b/redhat/configs/common/generic/CONFIG_CMDLINE_KUNIT_TEST @@ -1 +1 @@ -# CONFIG_CMDLINE_KUNIT_TEST is not set +CONFIG_CMDLINE_KUNIT_TEST=m diff --git a/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST b/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST +++ b/redhat/configs/common/generic/CONFIG_LINEAR_RANGES_TEST @@ -1 +1 @@ -# CONFIG_LINEAR_RANGES_TEST is not set +CONFIG_LINEAR_RANGES_TEST=m diff --git a/redhat/mod-internal.list b/redhat/mod-internal.list index blahblah..blahblah 100644 --- a/redhat/mod-internal.list +++ b/redhat/mod-internal.list @@ -18,11 +18,14 @@ test_bits test_kasan time_test fat_test +lib_test rational-test test_list_sort slub_kunit -lib_test +memcpy_kunit +dev_addr_lists_test kfence_test +test_hash locktorture mac80211_hwsim netdevsim -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1599

1 1

[OS-BUILD PATCHv2] [redhat] virtio: enable virtio-mem on x86-64 as tech-preview
by David Hildenbrand (via Email Bridge) 02 Feb '22

02 Feb '22

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

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2022