kernel July 2022

kernel@lists.fedoraproject.org

10 participants
49 discussions

[OS-BUILD PATCH] redhat/configs: Enable CONFIG_LZ4_COMPRESS
by Prarit Bhargava (via Email Bridge) 26 Jul '22

26 Jul '22

From: Prarit Bhargava <prarit(a)redhat.com> redhat/configs: Enable CONFIG_LZ4_COMPRESS CONFIG_LZ4_COMPRESS is needed for Virtual Data Optimizer (VDO). Suggested-by: Andrew Walsh <awalsh(a)redhat.com> Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff --git a/redhat/configs/ark/generic/CONFIG_LZ4_COMPRESS b/redhat/configs/ark/generic/CONFIG_LZ4_COMPRESS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/CONFIG_LZ4_COMPRESS @@ -0,0 +1 @@ +CONFIG_LZ4_COMPRESS=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1914

2 2

Re: ❌ FAIL: Test report for 5.18.13-200.fc36 (fedora-36)
by Ondrej Mosnacek 26 Jul '22

26 Jul '22

On Tue, Jul 26, 2022 at 8:11 AM <cki-project(a)redhat.com> wrote: > Hi, we tested your kernel and here are the results: > > Overall result: FAILED > Merge: OK > Compile: OK > Test: FAILED > > > You can find all the details about the test run at > https://datawarehouse.cki-project.org/kcidb/checkouts/48621 > > One or more kernel tests failed: > > Unrecognized or new issues: > s390x - selinux-policy: serge-testsuite > Logs: https://datawarehouse.cki-project.org/kcidb/tests/4492363 > make[2]: Entering directory '/root/selinux-testsuite/tests/module_load' cc -g -O0 -Wall -D_GNU_SOURCE -DHAVE_BPF -DHAVE_FS_WATCH_PERM finit_load.c -lselinux -o finit_load cc -g -O0 -Wall -D_GNU_SOURCE -DHAVE_BPF -DHAVE_FS_WATCH_PERM init_load.c -lselinux -o init_load make -C /lib/modules/5.18.13-200.fc36.s390x/build CC=gcc LD=ld.bfd M=/root/selinux-testsuite/tests/module_load make[3]: Entering directory '/usr/src/kernels/5.18.13-200.fc36.s390x' CC [M] /root/selinux-testsuite/tests/module_load/setest_module_load.o CC [M] /root/selinux-testsuite/tests/module_load/setest_module_request.o MODPOST /root/selinux-testsuite/tests/module_load/Module.symvers CC [M] /root/selinux-testsuite/tests/module_load/setest_module_load.mod.o LD [M] /root/selinux-testsuite/tests/module_load/setest_module_load.ko ld.bfd: cannot find arch/s390/lib/expoline/expoline.o: No such file or directory make[5]: *** [scripts/Makefile.modfinal:60: /root/selinux-testsuite/tests/module_load/setest_module_load.ko] Error 1 make[4]: *** [scripts/Makefile.modpost:140: __modpost] Error 2 make[3]: *** [Makefile:1757: modules] Error 2 make[3]: Leaving directory '/usr/src/kernels/5.18.13-200.fc36.s390x' make[2]: *** [Makefile:43: all] Error 2 make[2]: Leaving directory '/root/selinux-testsuite/tests/module_load' Looks like https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1912 will need to be picked also into the Fedora stable kernel branch(es). -- Ondrej Mosnacek Senior Software Engineer, Linux Security - SELinux kernel Red Hat, Inc.

1 0

❌ FAIL: Test report for 5.18.13-200.fc36 (fedora-36)
by cki-project＠redhat.com 26 Jul '22

26 Jul '22

Hi, we tested your kernel and here are the results: Overall result: FAILED Merge: OK Compile: OK Test: FAILED You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/48621 One or more kernel tests failed: Unrecognized or new issues: s390x - selinux-policy: serge-testsuite Logs: https://datawarehouse.cki-project.org/kcidb/tests/4492363 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: 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: aarch64 - Storage - block - storage fio numa x86_64 - Storage - block - storage fio numa Issue: Storage blktests - nvmeof-mp: FAIL: Configured NVMe target driver URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: x86_64 - Storage - blktests - nvmeof-mp 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: Podman: 110-history.bats: FAIL: CreatedSince and CreatedAt from image history should == image list URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: aarch64 - Podman system test - as root aarch64 - Podman system test - as user ppc64le - Podman system test - as root ppc64le - Podman system test - as user s390x - Podman system test - as root s390x - Podman system test - as user Issue: storage: software RAID testing: SELinux prevents mdadm URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: aarch64 - Storage - software RAID testing aarch64 - Storage - swraid simple_reshape ppc64le - Storage - software RAID testing ppc64le - Storage - swraid simple_reshape Issue: podman: cannot assign requested address URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: s390x - Podman system test - as user Issue: Storage - swraid simple_reshape: BUG bio-152 (Not tainted): Objects remaining in bio-152 on __kmem_cache_shutdown() URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: s390x - Storage - swraid simple_reshape Issue: SELinux prevents sendmail.service while running Memory function: kaslr URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/… Affected tests: aarch64 - Reboot test If you find a failure unrelated to your changes, please tag it at https://datawarehouse.cki-project.org . This will prevent the failures from being incorrectly reported in the future. If you don't have permissions to tag an issue, you can contact the CKI team or test maintainers. 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 `-' ______________________________________________________________________________

1 0

Error during compile of 5.19 rc7 kernel, seems to be bad name.
by stan 24 Jul '22

24 Jul '22

While compiling the latest kernel (which still wouldn't boot, working on it), I got the following warning message: Makefile.config:778: No libcrypto.h found, disables jitted code injection, please install openssl-devel or libssl-dev fatal: not a git repository (or any of the parent directories): .git ... repeats about 20 times I *do* have openssl-devel installed, but there is no libcrypto.h under /usr/include. There is a crypto.h at /usr/include/openssl/crypto.h I am thinking that this is an error in the makefile, the name changed out from under it.

1 0

5.18.14 and fedora
by Justin Forbes 23 Jul '22

23 Jul '22

I am not building 5,18.14 for Fedora, This is the upstream retbleed fix for stable. We have been carrying most of those patches since 5.18.11, and the last of them were picked up with the 5.18.13 build. The only thing in the upstream 5.18.14 build that is not in our 5.18.13 build is the version bump itself. Justin

1 0

[OS-BUILD PATCHv5 0/5] redhat/Makefile: Add dist-get-buildreqs target
by Prarit Bhargava (via Email Bridge) 22 Jul '22

22 Jul '22

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1900 The dist-buildreq-check target is useful in a few ways but results in unnecessary errors in many cases. Instead of stopping the build, add a new target 'dist-get-buildreqs' that can be called to get a list of uninstalled build requirements. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> --- redhat/docs/index.rst | 21 +++++++++++++++++++++ redhat/Makefile | 15 ++++++++++----- .gitlab-ci.yml | 21 +++++++++++++++++++++ 3 files changed, 52 insertions(+), 5 deletions(-)

3 9

[OS-BUILD PATCH 0/3] redhat/Makefile: BUILD_TARGET fixes
by Prarit Bhargava (via Email Bridge) 20 Jul '22

20 Jul '22

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1913 Update the BUILD_TARGET for dist-brew and eln. Also update the documentation as 'make dist-brew' should work everywhere. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> --- redhat/docs/faq.rst | 7 +++---- redhat/docs/index.rst | 8 ++++++++ redhat/self-test/data/rhel-2585cf9dfaad.el7 | 2 +- redhat/self-test/data/rhel-2585cf9dfaad.fc25 | 2 +- redhat/self-test/data/rhel-78e36f3b0dae.el7 | 2 +- redhat/self-test/data/rhel-78e36f3b0dae.fc25 | 2 +- redhat/self-test/data/rhel-df0cc57e057f.el7 | 2 +- redhat/self-test/data/rhel-df0cc57e057f.fc25 | 2 +- redhat/self-test/data/rhel-fce15c45d3fb.el7 | 2 +- redhat/self-test/data/rhel-fce15c45d3fb.fc25 | 2 +- redhat/Makefile | 10 +++++++--- 11 files changed, 26 insertions(+), 15 deletions(-)

1 3

[OS-BUILD PATCHv4 0/4] redhat/Makefile: Add dist-get-buildreqs target
by Prarit Bhargava (via Email Bridge) 20 Jul '22

20 Jul '22

1 4

F37 and unfortunate timing (a heads up)
by Justin Forbes 19 Jul '22

19 Jul '22

Fedora 37 does not branch from Rawhide until August 9th, and the 5.20 merge window will open up on August 1, that puts us in a bit of an odd situation. Fedora 37 will release on a 5.19 kernel because 5.20 is not expected to release before the final freeze begins. I don't think it would be wise to skip the daily builds through most of the merge window, so I plan to keep moving rawhide forward as usual. After the branch, I will move F37 back to a 5.19 kernel. Given this is a fairly unusual situation, it seemed worth sending out a heads up. Justin

1 0

Latest rawhide kernel, kernel-5.19.0-0.rc6.20220714git4a57a8400075.49.fc37.src.rpm, builds but won't boot
by stan 19 Jul '22

19 Jul '22

Hi, When I built the kernel-5.19.0-0.rc6.20220714git4a57a8400075.49.fc37.src.rpm using rpmbuild, it builds without any error, but fails to boot. The rc4 kernel with the same configuration with one exception runs fine. The exception is the new automatic timing mitigation configuration option. I turned it off, single user, no internet facing services, amd cpu (as i understand it, has vulnerabilities, but fewer). So, no complaints from the build process, but the kernel looks like it is going to boot (the drive light comes on), and then it just stops with a blank screen. Nothing in the journal since it fails at the start. I'll be building the rc6 kernel with the new option enabled to see if that fixes things, but the kernel should still run even if the automatic mitigation is turned off. Should I open a bugzilla for this?

5 10

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel July 2022