September 2021 - kernel - Fedora Mailing-Lists

[OS-BUILD PATCHv2] redhat: add documentation about the os-build rebase process

by Herton R. Krzesinski (via Email Bridge)

From: Herton R. Krzesinski <herton(a)redhat.com> redhat: add documentation about the os-build rebase process We have been rebasing os-build lately on each new major Linux upstream release. Add general instructions/guideline on how to do the rebase process on top of last upstream tag/commit. This also provides an explanation on why we are doing the rebase, provided by Don Zickus. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff --git a/redhat/docs/maintaining.rst b/redhat/docs/maintaining.rst index blahblah..blahblah 100644 --- a/redhat/docs/maintaining.rst +++ b/redhat/docs/maintaining.rst @@ -128,6 +128,66 @@ above Fedora build. To kick off manually run +Rebasing +-------- + +When a new major version of Linux is released upstream, we can rebase the +os-build branch. + +Rebasing from time to time, helps reduce the clutter of the extra changes +on top of upstream and future merge conflicts. This periodic rebase addresses +the needs of the Fedora community's desire to separate upstream from Fedora +specific changes, helps keep it clear what patches changed in the final form +upstream, and what a Fedora specific patch looks like currently as opposed to +split across various conflict patches. + +While rebasing has a negative effect on developer contribution, we believe +saving the rebase for the end of release cycle allows for minimal developer +contribution disruption while gaining the above advantages. + +This process is open to feedback for improvements. + +To do the os-build rebase, the following steps can be done: + +:: + + # Create a rebase branch from latest os-build branch and start the process + # For any conflicts that arise, check and fix them, following git instructions + git fetch origin + git checkout -b rebase origin/os-build + marker=$(cat redhat/marker) + git rebase $marker + + # After you finish the rebase, check the results against the current os-build + git diff origin/os-build.. + # If there are differences shown, you might have fixed conflicts wrongly or + # in a different way. To fix, you may want to add extra on top commits and + # rebase again interactively + <make change related to a previous commit to make it equal os-build> && git add + # create dummy commit + git commit + # You may need to create more than one commit, if changes are related to + # more than one previous commit. Then squash commits into the existing + # previous commits related to the change with: + git rebase -i $marker + + # Now cleanup any commits that we might have reverted, and release commits. + # When editor opens with the commit list in interactive mode, search for any + # commits starting with "Revert " in the subject and if they match a previous + # commit which is being reverted, you can remove both. For release commits, + # search commits with subject starting with "[redhat] kernel-" and delete/ + # remove them. + git rebase -i $marker + + # Check results again doing a diff against os-build branch. Because of cleanup + # in the previous step, some differences will appear now, and that's ok + # because of the removal of the release commits. The only differences that + # should appear are on Makefile.rhelver, redhat/kernel.changelog and + # redhat/marker + git diff origin/os-build.. + + # If differences shown are expected, we are ok and rebase is done. + :: TODO FILL ME IN -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387

2 years, 7 months

2
3
0 / 0

[OS-BUILD PATCH] redhat: add documentation about the os-build rebase process

by Herton R. Krzesinski (via Email Bridge)

From: Herton R. Krzesinski <herton(a)redhat.com> redhat: add documentation about the os-build rebase process We have been rebasing os-build lately on each new major Linux upstream release. Add general instructions/guideline on how to do the rebase process on top of last upstream tag/commit. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff --git a/redhat/docs/maintaining.rst b/redhat/docs/maintaining.rst index blahblah..blahblah 100644 --- a/redhat/docs/maintaining.rst +++ b/redhat/docs/maintaining.rst @@ -128,6 +128,58 @@ above Fedora build. To kick off manually run +Rebasing +-------- + +When a new major version of Linux is released upstream, we can rebase the +os-build branch. Keeping the process of merging from upstream without rebases +might make a future rebase more time consuming or harder to do, due growing +number of conflicts which happens with the ever growing changing of the tree, +which makes this periodic rebasing more desirable, and moves any needed conflict +resolution back into our patches on top of upstream and not on upstream merges +only. + +To do the os-build rebase, the following steps can be done: + +:: + + # Create a rebase branch from latest os-build branch and start the process + # For any conflicts that arise, check and fix them, following git instructions + git fetch origin + git checkout -b rebase origin/os-build + marker=$(cat redhat/marker) + git rebase $marker + + # After you finish the rebase, check the results against the current os-build + git diff origin/os-build.. + # If there are differences shown, you might have fixed conflicts wrongly or + # in a different way. To fix, you may want to add extra on top commits and + # rebase again interactively + <make change related to a previous commit to make it equal os-build> && git add + # create dummy commit + git commit + # You may need to create more than one commit, if changes are related to + # more than one previous commit. Then squash commits into the existing + # previous commits related to the change with: + git rebase -i $marker + + # Now cleanup any commits that we might have reverted, and release commits. + # When editor opens with the commit list in interactive mode, search for any + # commits starting with "Revert " in the subject and if they match a previous + # commit which is being reverted, you can remove both. For release commits, + # search commits with subject starting with "[redhat] kernel-" and delete/ + # remove them. + git rebase -i $marker + + # Check results again doing a diff against os-build branch. Because of cleanup + # in the previous step, some differences will appear now, and that's ok + # because of the removal of the release commits. The only differences that + # should appear are on Makefile.rhelver, redhat/kernel.changelog and + # redhat/marker + git diff origin/os-build.. + + # If differences shown are expected, we are ok and rebase is done. + :: TODO FILL ME IN -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387

2 years, 7 months

2
2
0 / 0

[OS-BUILD PATCH] redhat/configs: enable SYSTEM_BLACKLIST_KEYRING which is already enabled in rhel8 and Fedora 34

by Coiby Xu (via Email Bridge)

From: Coiby Xu <coxu(a)redhat.com> redhat/configs: enable SYSTEM_BLACKLIST_KEYRING which is already enabled in rhel8 and Fedora 34 Upstream Status: RHEL-only INTEGRITY_PLATFORM_KEYRING which depends on SYSTEM_BLACKLIST_KEYRING is needed to make use of the .platform keyring to verify kdump kernel image signature. By removing configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING, configs/common/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING which has CONFIG_SYSTEM_BLACKLIST_KEYRING=y will take precedence. Suggested-by: Ondrej Mosnacek <omosnace(a)redhat.com> Signed-off-by: Coiby Xu <coxu(a)redhat.com> diff --git a/redhat/configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING b/redhat/configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/ark/generic/CONFIG_SYSTEM_BLACKLIST_KEYRING +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_SYSTEM_BLACKLIST_KEYRING is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1385

2 years, 7 months

3
2
0 / 0

❌ FAIL: Test report for kernel 5.13.17-200.fc34 (fedora-34)

by CKI Project

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

2 years, 7 months

1
0
0 / 0

❌ FAIL: Test report for kernel 5.14.4-300.fc34 (fedora-34)

by CKI Project

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

2 years, 7 months

1
0
0 / 0

[OS-BUILD PATCHv2] redhat/configs: enable KEXEC_SIG which is already enabled in RHEL8 for s390x and x86_64

by Coiby Xu (via Email Bridge)

From: Coiby Xu <coxu(a)redhat.com> redhat/configs: enable KEXEC_SIG which is already enabled in RHEL8 for s390x and x86_64 Enable KEXEC_SIG for s390x and x86_64 which is already enabled in RHEL8. Note when building .src.rpm, process_configs.sh would error on unset config options. So CONFIG_KEXEC_SIG_FORCE files are added as well. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976835 Signed-off-by: Coiby Xu <coxu(a)redhat.com> diff --git a/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG b/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG @@ -0,0 +1 @@ +CONFIG_KEXEC_SIG=y diff --git a/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG_FORCE b/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG_FORCE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/CONFIG_KEXEC_SIG_FORCE @@ -0,0 +1 @@ +# CONFIG_KEXEC_SIG_FORCE is not set diff --git a/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG b/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG @@ -0,0 +1 @@ +CONFIG_KEXEC_SIG=y diff --git a/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG_FORCE b/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG_FORCE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/x86/CONFIG_KEXEC_SIG_FORCE @@ -0,0 +1 @@ +# CONFIG_KEXEC_SIG_FORCE is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1227

2 years, 7 months

6
8
0 / 0

[OS-BUILD PATCH] redhat: drop certificates that were deprecated after GRUB's BootHole flaw

by Herton R. Krzesinski (via Email Bridge)

From: Herton R. Krzesinski <herton(a)redhat.com> redhat: drop certificates that were deprecated after GRUB's BootHole flaw Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1994849 Since newer RHEL should already have newer enough grub versions, we don't need anymore to keep signing the kernel for secure boot with older keys for compatibility with older grub. The second signature also causes problems because the upstream kernel so far does not support checking more than one signature as reported on bug above, where kexec signature checking can fail in a secure boot enabled environment. More than one signature requires that we patch the kernel for it to work, but we don't need that now since we can drop the second signature. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff --git a/redhat/Makefile b/redhat/Makefile index blahblah..blahblah 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -277,10 +277,10 @@ sources-rh: $(TARBALL) generate-testpatch-tmp setup-source dist-configs-check README.rst \ $(SOURCES)/ @if [ "$(RELEASED_KERNEL)" -ne 0 ]; then \ - cp keys/redhatsecureboot{301,501,ca5,ca1}.cer $(SOURCES)/; \ + cp keys/redhatsecureboot{501,ca5}.cer $(SOURCES)/; \ cp keys/secureboot_{ppc,s390}.cer $(SOURCES)/; \ else \ - cp keys/redhatsecureboot{003,401,ca2,ca4}.cer $(SOURCES)/; \ + cp keys/redhatsecureboot{401,ca4}.cer $(SOURCES)/; \ fi @for KABIARCH in $(ARCH_LIST); do \ cp kabi/Module.kabi_$$KABIARCH $(SOURCES)/; \ 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 @@ -690,26 +690,21 @@ Source9: x509.genkey.fedora %if %{?released_kernel} Source10: redhatsecurebootca5.cer -Source11: redhatsecurebootca1.cer -Source12: redhatsecureboot501.cer -Source13: redhatsecureboot301.cer -Source14: secureboot_s390.cer -Source15: secureboot_ppc.cer - -%define secureboot_ca_1 %{SOURCE10} -%define secureboot_ca_0 %{SOURCE11} +Source11: redhatsecureboot501.cer +Source12: secureboot_s390.cer +Source13: secureboot_ppc.cer + +%define secureboot_ca_0 %{SOURCE10} %ifarch x86_64 aarch64 -%define secureboot_key_1 %{SOURCE12} -%define pesign_name_1 redhatsecureboot501 -%define secureboot_key_0 %{SOURCE13} -%define pesign_name_0 redhatsecureboot301 +%define secureboot_key_0 %{SOURCE11} +%define pesign_name_0 redhatsecureboot501 %endif %ifarch s390x -%define secureboot_key_0 %{SOURCE14} +%define secureboot_key_0 %{SOURCE12} %define pesign_name_0 redhatsecureboot302 %endif %ifarch ppc64le -%define secureboot_key_0 %{SOURCE15} +%define secureboot_key_0 %{SOURCE13} %define pesign_name_0 redhatsecureboot303 %endif @@ -717,16 +712,11 @@ Source15: secureboot_ppc.cer %else Source10: redhatsecurebootca4.cer -Source11: redhatsecurebootca2.cer -Source12: redhatsecureboot401.cer -Source13: redhatsecureboot003.cer - -%define secureboot_ca_1 %{SOURCE10} -%define secureboot_ca_0 %{SOURCE11} -%define secureboot_key_1 %{SOURCE12} -%define pesign_name_1 redhatsecureboot401 -%define secureboot_key_0 %{SOURCE13} -%define pesign_name_0 redhatsecureboot003 +Source11: redhatsecureboot401.cer + +%define secureboot_ca_0 %{SOURCE10} +%define secureboot_key_0 %{SOURCE11} +%define pesign_name_0 redhatsecureboot401 # released_kernel %endif @@ -1630,9 +1620,7 @@ BuildKernel() { fi %ifarch x86_64 aarch64 - %pesign -s -i $SignImage -o vmlinuz.tmp -a %{secureboot_ca_0} -c %{secureboot_key_0} -n %{pesign_name_0} - %pesign -s -i vmlinuz.tmp -o vmlinuz.signed -a %{secureboot_ca_1} -c %{secureboot_key_1} -n %{pesign_name_1} - rm vmlinuz.tmp + %pesign -s -i $SignImage -o vmlinuz.signed -a %{secureboot_ca_0} -c %{secureboot_key_0} -n %{pesign_name_0} %endif %ifarch s390x ppc64le if [ -x /usr/bin/rpm-sign ]; then @@ -2097,13 +2085,7 @@ BuildKernel() { # Red Hat UEFI Secure Boot CA cert, which can be used to authenticate the kernel mkdir -p $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer - %ifarch x86_64 aarch64 - install -m 0644 %{secureboot_ca_0} $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer/kernel-signing-ca-20200609.cer - install -m 0644 %{secureboot_ca_1} $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer/kernel-signing-ca-20140212.cer - ln -s kernel-signing-ca-20200609.cer $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer/kernel-signing-ca.cer - %else - install -m 0644 %{secureboot_ca_0} $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer/kernel-signing-ca.cer - %endif + install -m 0644 %{secureboot_ca_0} $RPM_BUILD_ROOT%{_datadir}/doc/kernel-keys/$KernelVer/kernel-signing-ca.cer %ifarch s390x ppc64le if [ $DoModules -eq 1 ]; then if [ -x /usr/bin/rpm-sign ]; then diff --git a/redhat/keys/redhatsecureboot003.cer b/redhat/keys/redhatsecureboot003.cer deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/keys/redhatsecureboot003.cer +++ /dev/null Binary files a/redhat/keys/redhatsecureboot003.cer and /dev/null differ diff --git a/redhat/keys/redhatsecureboot301.cer b/redhat/keys/redhatsecureboot301.cer deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/keys/redhatsecureboot301.cer +++ /dev/null Binary files a/redhat/keys/redhatsecureboot301.cer and /dev/null differ diff --git a/redhat/keys/redhatsecurebootca1.cer b/redhat/keys/redhatsecurebootca1.cer deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/keys/redhatsecurebootca1.cer +++ /dev/null Binary files a/redhat/keys/redhatsecurebootca1.cer and /dev/null differ diff --git a/redhat/keys/redhatsecurebootca2.cer b/redhat/keys/redhatsecurebootca2.cer deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/keys/redhatsecurebootca2.cer +++ /dev/null Binary files a/redhat/keys/redhatsecurebootca2.cer and /dev/null differ -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1321

2 years, 7 months

4
7
0 / 0

✅ PASS: Test report for kernel 5.13.16-200.fc34 (fedora-34)

by CKI Project

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.13.16-200.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=75601061 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. ✅ 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 ⚡⚡⚡ 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 ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage blktests - nvmeof-mp 🚧 ❌ Storage blktests - srp 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ❌ storage: software RAID testing Host 2: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon s390x: Host 1: ✅ Boot test ✅ Reboot test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests - blk 🚧 ✅ Storage blktests - nvme-tcp 🚧 ✅ Storage blktests - nvmeof-mp 🚧 💥 Storage blktests - srp 🚧 ⚡⚡⚡ stress: stress-ng x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ 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 blktests - nvmeof-mp 🚧 ⚡⚡⚡ Storage blktests - srp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng Host 2: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP - cve ✅ LTP - sched ✅ LTP - syscalls ✅ LTP - can ✅ LTP - commands ✅ LTP - containers ✅ LTP - dio ✅ LTP - fs ✅ LTP - fsx ✅ LTP - math ✅ LTP - hugetlb ✅ LTP - mm ✅ LTP - nptl ✅ LTP - pty ✅ LTP - ipc ✅ LTP - tracing ✅ 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: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp 🚧 ⚡⚡⚡ Storage blktests - srp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests - blk 🚧 ⚡⚡⚡ Storage blktests - nvme-tcp 🚧 ⚡⚡⚡ Storage blktests - nvmeof-mp 🚧 ⚡⚡⚡ Storage blktests - srp 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

2 years, 7 months

1
0
0 / 0

[OS-BUILD PATCHv2 0/2] x86_64: Enable Elkhart Lake Quadrature Encoder Peripheral support

by Prarit Bhargava (via Email Bridge)

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1383 Enable Elkhart Lake Quadrature Encoder Peripheral support for both RHEL and Fedora. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> --- redhat/configs/common/generic/x86/x86_64/CONFIG_COUNTER | 1 + redhat/configs/common/generic/x86/x86_64/CONFIG_INTEL_QEP | 1 + redhat/configs/common/generic/x86/x86_64/CONFIG_INTERRUPT_CNT | 1 + redhat/configs/common/generic/CONFIG_DMA_RESTRICTED_POOL | 1 + redhat/configs/pending-common/generic/CONFIG_DMA_RESTRICTED_POOL | 11 ---------- 5 files changed, 4 insertions(+), 11 deletions(-)

2 years, 7 months

3
4
0 / 0

[OS-BUILD PATCH] x86_64: Enable Elkhart Lake Quadrature Encoder Peripheral support

by Prarit Bhargava (via Email Bridge)

From: Prarit Bhargava <prarit(a)redhat.com> x86_64: Enable Elkhart Lake Quadrature Encoder Peripheral support Enable Elkhart Lake Quadrature Encoder Peripheral support for both RHEL and Fedora. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/redhat/configs/common/generic/x86/x86_64/CONFIG_COUNTER b/redhat/configs/common/generic/x86/x86_64/CONFIG_COUNTER new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_COUNTER @@ -0,0 +1 @@ +CONFIG_COUNTER=m diff --git a/redhat/configs/common/generic/x86/x86_64/CONFIG_INTEL_QEP b/redhat/configs/common/generic/x86/x86_64/CONFIG_INTEL_QEP new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_INTEL_QEP @@ -0,0 +1 @@ +CONFIG_INTEL_QEP=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1383

2 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel September 2021