Hi, we tested your kernel and here are the results:
Overall result: PASSED
Merge: OK
Compile: OK
Test: OK
Tested-by: CKI Project <cki-project(a)redhat.com>
Kernel information:
Brew / Koji Task ID: 95767337
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/64602
One or more kernel tests failed:
We also see the following known issues which are not related to your changes:
Issue: [upstream] [aarch64] [ampere] [altramax] 5.19.0-rc8 - panic __efi_rt_asm_wrapper+0x2c/0x4c efi_call_rts+0x260/0x3d4
URL: https://lore.kernel.org/all/CA+QYu4r50dDuTyWbAqjjbvniW6O6Nr4V+1A_G2f37EVHJt…
Affected tests:
aarch64 - Boot test
Issue: Storage block - storage fio numa: Performance comparison: min:40535 * 1.15 < max:81259
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2032094
Affected tests:
x86_64 - Storage - block - storage fio numa
Issue: Storage blktests - blk: scsi/007: Reading from scsi_debug failed
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2027550
Affected tests:
s390x - Storage - blktests - blk
Issue: NFS Connectathon: SELinux prevents rpcbind
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/…
Affected tests:
s390x - NFS Connectathon
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hi, we tested your kernel and here are the results:
Overall result: FAILED
Merge: OK
Compile: OK
Test: FAILED
Kernel information:
Brew / Koji Task ID: 95762390
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/64582
One or more kernel tests failed:
Unrecognized or new issues:
aarch64 - NFS Connectathon
Logs: https://datawarehouse.cki-project.org/kcidb/tests/6549399
We also see the following known issues which are not related to your changes:
Issue: Storage blktests - blk: scsi/007: Reading from scsi_debug failed
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2027550
Affected tests:
aarch64 - Storage - blktests - blk
x86_64 - Storage - blktests - blk
Issue: Storage block - storage fio numa: Performance comparison: min:40535 * 1.15 < max:81259
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2032094
Affected tests:
x86_64 - Storage - block - storage fio numa
Issue: xfstests - cifsv3.11: generic/001: Kernel stack is corrupted in: cifs_get_inode_info+0xbcc/0xbe0 [cifs]
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/…
Affected tests:
ppc64le - CIFS Connectathon
x86_64 - CIFS Connectathon
x86_64 - xfstests - cifsv3.11
Issue: avc: denied { name_bind } for pid=897864 comm="rpcbind" src=63924 scontext=system_u:system_r:rpcbind_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=udp_socket permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1983604#c3
Affected tests:
x86_64 - xfstests - nfsv4.2
Issue: NFS Connectathon: SELinux prevents rpcbind
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/…
Affected tests:
s390x - NFS Connectathon
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/configs: Enable CRYPTO_CURVE25519 in ark
Enable CRYPTO_CURVE25519 in ark based on the feedback from a previous
merge request [1]. This requires a minor cleanup of the fedora and ark
generic files.
[1] https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_…
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/configs/ark/generic/CONFIG_CRYPTO_CURVE25519 b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CURVE25519
rename from redhat/configs/ark/generic/CONFIG_CRYPTO_CURVE25519
rename to redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CURVE25519
index blahblah..blahblah 100644
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_CURVE25519
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CURVE25519
diff --git a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CURVE25519 b/redhat/configs/common/CONFIG_CRYPTO_CURVE25519
rename from redhat/configs/fedora/generic/CONFIG_CRYPTO_CURVE25519
rename to redhat/configs/common/CONFIG_CRYPTO_CURVE25519
index blahblah..blahblah 100644
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CURVE25519
+++ b/redhat/configs/common/CONFIG_CRYPTO_CURVE25519
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2225
From: Vitaly Kuznetsov on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2175
The new 'kernel-unified-virt' sub-RPM is added on x86_64 targets.
This matches the following CS9 request:
https://gitlab.com/redhat/centos-stream/src/kernel/centos-
stream-9/-/merge_requests/1736
This contains an EFI application that provides a combined vmlinux,
initrd and cmdline, as a so called 'unified kernel image'. The
spec for this is defined by the boot loader specification
https://systemd.io/BOOT_LOADER_SPECIFICATION/#type-2-efi-unified-kernel-
images
Note: the newly introduced sub-package just puts UKI to /boot/efi/EFI/Linux/,
it is supposed to be booted directly from firmware or directly from shim and
this part is environement specific and not (yet) automated.
Based-on-patch-by: Daniel P. Berrangé <berrange(a)redhat.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets(a)redhat.com>
---
redhat/Makefile | 1 +
redhat/dracut-virt.conf | 35 ++++++++
redhat/kernel.spec.template | 179 +++++++++++++++++++++++++++++++++++++------
3 files changed, 190 insertions(+), 25 deletions(-)
From: Gerd Hoffmann on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2179
NOTE: Truncated patchset since committer email 'kernel-team(a)fedoraproject.org'
does not match the submitter's GitLab public email address
'kraxel(a)redhat.com'.
All kernel modules plus support files (such as the files generated
by depmod) are moved to the new kernel-modules-core sub-rpm.
The kernel binary plus support files stay in the kernel-core sub-rpm.
This essentially includes the files which are copied over to /boot by
the kernel-install utility (vmlinuz, System.map, ...).
With this in place we have a strict separation between sub-rpms carrying
a kernel image and sub-rpms carrying kernel modules. This should make it
easier to use alternative kernel image packages, for example an unified
kernel.
---
redhat/kernel.changelog-9.99 | 5 ++++
redhat/kernel.spec.template | 55 ++++++++++++++++++++++++++++++++++++++++---
scripts/head-object-list.txt | 1 +
Makefile.rhelver | 2 +-
4 files changed, 58 insertions(+), 5 deletions(-)
Hi, we tested your kernel and here are the results:
Overall result: PASSED
Merge: OK
Compile: OK
Test: OK
Tested-by: CKI Project <cki-project(a)redhat.com>
Kernel information:
Brew / Koji Task ID: 95722720
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/64360
One or more kernel tests failed:
We also see the following known issues which are not related to your changes:
Issue: Storage block - storage fio numa: Performance comparison: min:40535 * 1.15 < max:81259
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2032094
Affected tests:
x86_64 - Storage - block - storage fio numa
Issue: avc: denied { name_bind } for pid=897864 comm="rpcbind" src=63924 scontext=system_u:system_r:rpcbind_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=udp_socket permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1983604#c3
Affected tests:
x86_64 - xfstests - nfsv4.2
Issue: NFS Connectathon: SELinux prevents rpcbind
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/…
Affected tests:
aarch64 - NFS Connectathon
ppc64le - NFS Connectathon
Issue: [upstream] [aarch64] [ampere] [altramax] 5.19.0-rc8 - panic __efi_rt_asm_wrapper+0x2c/0x4c efi_call_rts+0x260/0x3d4
URL: https://lore.kernel.org/all/CA+QYu4r50dDuTyWbAqjjbvniW6O6Nr4V+1A_G2f37EVHJt…
Affected tests:
aarch64 - Boot test
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/docs: Add FAQ entry for booting between Fedora & ELN/RHEL kernels
Add an FAQ entry that provides some simple debugging suggestions for
booting between Fedora and ELN/RHEL kernels.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/docs/faq.rst b/redhat/docs/faq.rst
index blahblah..blahblah 100644
--- a/redhat/docs/faq.rst
+++ b/redhat/docs/faq.rst
@@ -35,8 +35,19 @@ resolve this properly.
Please notify us on kernel(a)lists.fedoraproject.org or file an issue at
https://gitlab.com/cki-project/kernel-ark/-/issues.
+3. I am booting an ELN/RHEL kernel on Fedora (or vice versa) and the kernel won't boot. What do I do now?
+----------------------------------------------------------------------------------------------------------
-3. How does an MR get reviewed?
+This is not uncommon and may be due to a config difference between RHEL and Fedora. One key difference between the two kernels is that Fedora has enabled CONFIG_BTRFS where ELN/RHEL has not, and as a result ELN/RHEL kernels will not mount Fedora BTRFS filesystems. If you are booting the ELN/RHEL kernel config on Fedora you must change these configuration values in the .config:
+
+.. code-block:: sh
+
+ CONFIG_BTRFS=y
+ CONFIG_BTRFS_FS_POSIX_ACL=y
+
+If that change doesn't resolve the boot failure, users should attempt to "flip" configs to determine the difference between the two flavors before reporting bugs. The maintainers acknowledge that this can be a time consuming process but it is left to the user to resolve config differences when cross booting between flavors.
+
+4. How does an MR get reviewed?
-------------------------------
Anything Fedora specific (configs, custom patches, scripts) will be decided
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2239
From: Prarit Bhargava <prarit(a)redhat.com>
redhat/docs: Add FAQ entry for booting between Fedora & ELN/RHEL kernels
Add an FAQ entry that provides some simple debugging suggestions for
booting between Fedora and ELN/RHEL kernels.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
diff --git a/redhat/docs/faq.rst b/redhat/docs/faq.rst
index blahblah..blahblah 100644
--- a/redhat/docs/faq.rst
+++ b/redhat/docs/faq.rst
@@ -35,8 +35,18 @@ resolve this properly.
Please notify us on kernel(a)lists.fedoraproject.org or file an issue at
https://gitlab.com/cki-project/kernel-ark/-/issues.
+3. I am booting an ELN/RHEL kernel on Fedora (or vice versa) and the kernel won't boot. What do I do now?
-3. How does an MR get reviewed?
+This is not uncommon and may be due to a config difference between RHEL and Fedora. One key difference between the two kernels is that Fedora has enabled CONFIG_BTRFS where ELN/RHEL has not, and as a result ELN/RHEL kernels will not mount Fedora BTRFS filesystems. If you are booting the ELN/RHEL kernel config on Fedora you must change these configuration values in the .config:
+
+.. code-block:: sh
+
+ CONFIG_BTRFS=y
+ CONFIG_BTRFS_FS_POSIX_ACL=y
+
+If that change doesn't resolve the boot failure, users should attempt to "flip" configs to determine the difference between the two flavors before reporting bugs. The maintainers acknowledge that this can be a time consuming process but it is left to the user to resolve config differences when cross booting between flavors.
+
+4. How does an MR get reviewed?
-------------------------------
Anything Fedora specific (configs, custom patches, scripts) will be decided
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2239
From: Gerd Hoffmann on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2179
NOTE: Truncated patchset since committer email 'kernel-team(a)fedoraproject.org'
does not match the submitter's GitLab public email address
'kraxel(a)redhat.com'.
All kernel modules plus support files (such as the files generated
by depmod) are moved to the new kernel-modules-core sub-rpm.
The kernel binary plus support files stay in the kernel-core sub-rpm.
This essentially includes the files which are copied over to /boot by
the kernel-install utility (vmlinuz, System.map, ...).
With this in place we have a strict separation between sub-rpms carrying
a kernel image and sub-rpms carrying kernel modules. This should make it
easier to use alternative kernel image packages, for example an unified
kernel.
---
redhat/kernel.changelog-9.99 | 5 ++++
redhat/kernel.spec.template | 55 ++++++++++++++++++++++++++++++++++++++++---
scripts/head-object-list.txt | 1 +
Makefile.rhelver | 2 +-
4 files changed, 58 insertions(+), 5 deletions(-)