kernel November 2023

kernel@lists.fedoraproject.org

5 participants
31 discussions

✅ PASS: Test report for 6.5.12-100.fc37 (kernel-fedora)
by cki-project＠redhat.com 20 Nov '23

20 Nov '23

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: 109318980 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/115761 One or more kernel tests failed: We also see the following known issues which are not related to your changes: Issue: NFS Connectathon: SELinux prevents rpcbind URL: https://bugzilla.redhat.com/1758147 Affected tests: ppc64le - Filesystem - 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 `-' ______________________________________________________________________________

1 0

[OS-BUILD PATCHv4 0/3] redhat: introduce RH_KABI_EXCLUDE_WITH_SIZE and enable size checks
by Sabrina Dubroca (via Email Bridge) 17 Nov '23

17 Nov '23

From: Sabrina Dubroca on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1619 This MR introduces a new kABI macro, RH_KABI_EXCLUDE_WITH_SIZE. The implementation is identical to RH_KABI_EXTEND_WITH_SIZE, but the meaning is more in line with RH_KABI_EXCLUDE. The size check and reserved space allows us to exclude an element embedded inside a kABI-protected structure while reserving space for it to grow in the future. The size checks that are part of multiple kABI macros are currently not enabled because the config option to turn them on is missing. Those size checks only make sense on regular builds, so they're disabled on debug kernels. Signed-off-by: Sabrina Dubroca <sdubroca(a)redhat.com> --- include/linux/rh_kabi.h | 30 +++++++++- redhat/configs/rhel/debug/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/rhel/generic/s390x/zfcpdump/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/rhel/generic/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/rhel/rt/generic/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + Kconfig.redhat | 9 +++ 6 files changed, 41 insertions(+), 2 deletions(-)

2 6

[OS-BUILD PATCHv3 0/2] redhat: introduce RH_KABI_EXCLUDE_WITH_SIZE and enable size checks
by Sabrina Dubroca (via Email Bridge) 16 Nov '23

16 Nov '23

From: Sabrina Dubroca on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1619 This MR introduces a new kABI macro, RH_KABI_EXCLUDE_WITH_SIZE. The implementation is identical to RH_KABI_EXTEND_WITH_SIZE, but the meaning is more in line with RH_KABI_EXCLUDE. The size check and reserved space allows us to exclude an element embedded inside a kABI-protected structure while reserving space for it to grow in the future. The size checks that are part of multiple kABI macros are currently not enabled because the config option to turn them on is missing. Those size checks only make sense on regular builds, so they're disabled on debug kernels. Signed-off-by: Sabrina Dubroca <sdubroca(a)redhat.com> --- include/linux/rh_kabi.h | 26 ++++++++++ redhat/configs/ark/debug/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/ark/generic/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/ark/kgcov/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + redhat/configs/common/generic/CONFIG_RH_KABI_SIZE_ALIGN_CHECKS | 1 + Kconfig.redhat | 9 +++ 6 files changed, 39 insertions(+), 0 deletions(-)

4 7

[OS-BUILD PATCH 0/0] [redhat] New configs in sound/soc
by CKI Gitlab (via Email Bridge) 13 Nov '23

13 Nov '23

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2805 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. Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. Symbol: SND_SOC_AW87390 [=n] Type : tristate Defined at sound/soc/codecs/Kconfig:673 Prompt: Soc Audio for awinic aw87390 Depends on: SOUND [=m] && SND [=m] && SND_SOC [=m] && I2C [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> CODEC drivers -> Soc Audio for awinic aw87390 (SND_SOC_AW87390 [=n]) Selects: REGMAP_I2C [=m] && SND_SOC_AW88395_LIB [=n] Implied by [n]: - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] --- Symbol: SND_SOC_AW88399 [=n] Type : tristate Defined at sound/soc/codecs/Kconfig:684 Prompt: Soc Audio for awinic aw88399 Depends on: SOUND [=m] && SND [=m] && SND_SOC [=m] && I2C [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> CODEC drivers -> Soc Audio for awinic aw88399 (SND_SOC_AW88399 [=n]) Selects: CRC8 [=m] && REGMAP_I2C [=m] && GPIOLIB [=y] && SND_SOC_AW88395_LIB [=n] Implied by [n]: - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] --- Symbol: SND_SOC_INTEL_AVS_MACH_RT5514 [=n] Type : tristate Defined at sound/soc/intel/avs/boards/Kconfig:128 Prompt: rt5514 in I2S mode Depends on: SOUND [=m] && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_AVS [=m] && I2C [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> Intel AVS driver (SND_SOC_INTEL_AVS [=m]) -> Intel AVS Machine drivers -> rt5514 in I2S mode (SND_SOC_INTEL_AVS_MACH_RT5514 [=n]) Selects: SND_SOC_RT5514 [=m] --- Symbol: SND_SOC_INTEL_SOF_DA7219_MACH [=n] Type : tristate Defined at sound/soc/intel/boards/Kconfig:616 Prompt: SOF with DA7219 codec in I2S Mode Depends on: SOUND [=m] && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && I2C [=y] && ACPI [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) && SND_HDA_CODEC_HDMI [=m] && SND_SOC_SOF_HDA_AUDIO_CODEC [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y]) -> SOF with DA7219 codec in I2S Mode (SND_SOC_INTEL_SOF_DA7219_MACH [=n]) Selects: SND_SOC_INTEL_HDA_DSP_COMMON [=m] && SND_SOC_DA7219 [=m] && SND_SOC_MAX98357A [=m] && SND_SOC_MAX98373_I2C [=m] && SND_SOC_DMIC [=m] && SND_SOC_INTEL_SOF_MAXIM_COMMON [=m] && SND_SOC_INTEL_SOF_SSP_COMMON [=m] --- Symbol: SND_SOC_RTQ9128 [=n] Type : tristate Defined at sound/soc/codecs/Kconfig:1665 Prompt: Richtek RTQ9128 45W Digital Input Amplifier Depends on: SOUND [=m] && SND [=m] && SND_SOC [=m] && I2C [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> CODEC drivers -> Richtek RTQ9128 45W Digital Input Amplifier (SND_SOC_RTQ9128 [=n]) Selects: REGMAP [=y] Implied by [n]: - SND_SOC_ALL_CODECS [=n] && SOUND [=m] && SND [=m] && SND_SOC [=m] && COMPILE_TEST [=n] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/pending-rhel/generic/CONFIG_MFD_CS42L43_SDW | 1 - redhat/configs/pending-rhel/generic/CONFIG_SND_SOC_AW87390 | 19 ---------- redhat/configs/pending-rhel/generic/CONFIG_SND_SOC_AW88399 | 19 ---------- redhat/configs/pending-rhel/generic/CONFIG_SND_SOC_INTEL_AVS_MACH_RT5514 | 18 --------- redhat/configs/pending-rhel/generic/CONFIG_SND_SOC_INTEL_SOF_DA7219_MACH | 17 -------- redhat/configs/pending-rhel/generic/CONFIG_SND_SOC_RTQ9128 | 19 ---------- redhat/configs/rhel/generic/CONFIG_MFD_CS42L43_SDW | 2 +- redhat/configs/rhel/generic/CONFIG_SND_SOC_AW87390 | 1 + redhat/configs/rhel/generic/CONFIG_SND_SOC_AW88399 | 1 + redhat/configs/rhel/generic/CONFIG_SND_SOC_INTEL_AVS_MACH_RT5514 | 1 + redhat/configs/rhel/generic/CONFIG_SND_SOC_INTEL_SOF_DA7219_MACH | 1 + redhat/configs/rhel/generic/CONFIG_SND_SOC_RTQ9128 | 1 + 12 files changed, 6 insertions(+), 94 deletions(-)

2 1

[Test Days] Kernel 6.6 2023-11-12 through 2023-11-19
by Sumantro Mukherjee 13 Nov '23

13 Nov '23

Hey All, I would like to invite all of you to participate in the Kernel 6.6 Test week is happening from 2023-11-12 to 2023-11-19. It's fairly simple, head over to the wiki [0] and read in detail about the test week and simply run the test case mentioned in[1] and enter your results. As usual, the Fedora QA team will hangout at #fedora-test-day(a)libera.chat for questions and discussion. [0] http://fedoraproject.org/wiki/Test_Day:2023-11-12_Kernel_6.6_Test_Week [1] https://testdays.fedoraproject.org/events/172 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

module signing: Changing to MODULE_SIG_SHA3_512
by Prarit Bhargava 09 Nov '23

09 Nov '23

Hey everyone, The current kernel configs generate # CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y # CONFIG_MODULE_SIG_SHA256 is not set # CONFIG_MODULE_SIG_SHA384 is not set CONFIG_MODULE_SIG_SHA512=y # CONFIG_MODULE_SIG_SHA3_256 is not set # CONFIG_MODULE_SIG_SHA3_384 is not set # CONFIG_MODULE_SIG_SHA3_512 is not set CONFIG_MODULE_SIG_HASH="sha512" With https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2802 we can strengthen the module signing algorithm to CONFIG_MODULE_SIG_SHA3_512. I'd like to do this before Fedora40, as it will be the basis of centos-stream-10 and RHEL10. Thoughts or concerns? P.

2 5

[OS-BUILD PATCH 0/0] Drop custom mode for System.map file
by Zbigniew Jędrzejewski-Szmek (via Email Bridge) 09 Nov '23

09 Nov '23

From: Zbigniew Jędrzejewski-Szmek on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2819 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. Mode 0600 was introduced in [1], with the justification that "You can just chmod 644 them later if you (unlikely) need them without root.". The time where a different mode is needed has come ;) I'm building initrd images as part of the mkosi project [2], and in general mkosi is designed to be executed unprivileged, and currently this fails when copying in the kernel module files, because System.map is not readable. Mode 0600 is not useful for files that are packaged, anyone can trivially get the file from the web, or even from the dnf cache, etc. The packaging guidelines [3] say: "Inside of /usr [...] [files] MUST be universally readable." A similar case came up recently with polkit rules [4]. Apparently RH security folks found the change acceptable. Also, at least on Debian System.map is 0644. [1] https://src.fedoraproject.org/rpms/kernel/c/d287769cc9dbdad68eb0123b149e8c 8edae4632f [2] https://github.com/systemd/mkosi/pull/2040 [3] https://docs.fedoraproject.org/en-US/packaging- guidelines/#_file_permissions [4] https://gitlab.freedesktop.org/polkit/polkit/-/merge_requests/153 --- redhat/kernel.spec.template | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)

1 0

[OS-BUILD PATCH] aarch64: enable uki
by Gerd Hoffmann (via Email Bridge) 09 Nov '23

09 Nov '23

From: Gerd Hoffmann <kraxel(a)redhat.com> aarch64: enable uki Now, with CONFIG_EFI_ZBOOT enabled and aarch64 kernels being self-unpacking efi binaries instead of gzipped images, building aarch64 UKIs actually works. Flip the switch and enable them. Signed-off-by: Gerd Hoffmann <kraxel(a)redhat.com> diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index blahblah..blahblah 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -285,7 +285,7 @@ Summary: The Linux kernel # Want to build a vanilla kernel build without any non-upstream patches? %define with_vanilla %{?_with_vanilla: 1} %{?!_with_vanilla: 0} -%ifarch x86_64 +%ifarch x86_64 aarch64 %define with_efiuki %{?_without_efiuki: 0} %{?!_without_efiuki: 1} %else %define with_efiuki 0 -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2818

2 8

✅ PASS: Test report for 6.5.11-100.fc37 (kernel-fedora)
by cki-project＠redhat.com 08 Nov '23

08 Nov '23

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: 108766203 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/113945 One or more kernel tests failed: We also see the following known issues which are not related to your changes: Issue: NFS Connectathon: SELinux prevents rpcbind URL: https://bugzilla.redhat.com/1758147 Affected tests: ppc64le - Filesystem - 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 `-' ______________________________________________________________________________

1 0

[Testdays] Call for Fedora Linux 40 testing events
by Sumantro Mukherjee 08 Nov '23

08 Nov '23

Hi Fedora users, developers, and friends! It's time to start thinking about Test Days for Fedora 40. For anyone who isn't aware, a Test Day is an event usually focused around IRC for interaction and a Wiki page for instructions and results, with the aim being to get a bunch of interested users and developers together to test a specific feature or area of the distribution. You can run a Test Day on just about anything for which it would be useful to do some fairly focused testing in 'real time' with a group of testers; it doesn't have to be code, for instance, we often run Test Days for l10n/i18n topics. For more information on Test Days, see https://fedoraproject.org/wiki/QA/Test_Days . Anyone who wants to can host their own Test Day, or you can request that the QA group helps you out with organization or any combination of the two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's an example https://pagure.io/fedora-qa/issue/624 . For instructions on hosting a Test Day, see https://fedoraproject.org/wiki/QA/SOP_Test_Day_management . You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days . There are many slots open right now. Consider the development schedule, though, in deciding when you want to run your Test Day - for some topics you may want to avoid the time before the Beta release or the time after the feature freeze or the Final Freeze. We normally aim to schedule Test Days on Thursdays; however, if you want to run a series of related Test Days, it's often a good idea to do something like Tuesday / Wednesday / Thursday of the same week (this is how we usually run the X Test Week, for instance). If all the Thursday slots fill up but more people want to run Test Days, we will open up Tuesday slots as overflows. And finally, if you really want to run a Test Day in a specific time frame due to the development schedule, but the Thursday slot for that week is full, we can add a slot on another day. We're flexible! Just put in your ticket the date or time frame you'd like, and we'll figure it out from there. If you don't want to run your own Test Day, but you are willing to help with another, feel free to join one or more of already accepted Test Days: GNOME Test Day* i18n Test Day* Kernel Test Week(s)* Upgrade Test Day* IoT Test Week* Cloud Test Day* Fedora CoreOS Test Week* And don't be afraid, there are a lot of more slots available for your own Test Day! [*] These are the test days we run generally to make sure everything is working fine, the dates get announced as we move into the release cycle. If you have any questions about the Test Day process, please don't hesitate to contact me or any member of the Fedora QA team on test at lists.fedoraproject.org or in #fedora-qa on IRC. Thanks! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel November 2023