kernel March 2024

kernel@lists.fedoraproject.org

12 participants
64 discussions

[OS-BUILD PATCH] Add wildcard macros -baseonly -gcov
by Don Zickus (via Email Bridge) 18 Sep '24

18 Sep '24

From: Don Zickus <dzickus(a)redhat.com> Add wildcard macros -baseonly -gcov There are multiple usecases for -baseonly and -gcov on various targets in the Makefile. Instead of calling those targets out repeatedly, lets generalize them a bit. Allow adding -baseonly and -gcov to: dist-rpm dist-srpm dist-brew dist-koji distg-brew distg-koji Gcov is useful for adding code coverage. Baseonly is useful to only build the kernel for debugging purposes without userspace tools. Signed-off-by: Don Zickus <dzickus(a)redhat.com> diff --git a/redhat/Makefile b/redhat/Makefile index blahblah..blahblah 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -297,6 +297,12 @@ dist-sources: dist-kabi dist-kabi-dup sources-rh dist-test-patch: generate-testpatch-tmp @mv $(TESTPATCH).tmp $(TESTPATCH); +%-baseonly: RPMBUILDOPTS=--target $(MACH) --without debug --without debuginfo --without vdso_install --without bpftool --without perf --without tools --without selftests -bb +%-baseonly: BUILDOPTS+=-debug -debuginfo -vdso_install -bpftool -perf -tools -selftests + +%-gcov: BUILDID=".gcov" +%-gcov: BUILDOPTS+="+gcov" + do-rpmbuild: dist-sources $(RPMBUILD) --define "_sourcedir $(SOURCES)" --define "_builddir $(RPM)/BUILD" --define "_srcrpmdir $(RPM)/SRPMS" --define "_rpmdir $(RPM)/RPMS" --define "_specdir $(RPM)/SPECS" --define "dist $(DIST)" $(RPMBUILDOPTS) $(RPM)/SOURCES/$(PACKAGE_NAME).spec @@ -306,9 +312,9 @@ dist-all-rpms: dist-sources do-rpmbuild dist-srpm: RPMBUILDOPTS=--nodeps -bs dist-srpm: dist-sources do-rpmbuild -dist-srpm-gcov: BUILDID=".gcov" -dist-srpm-gcov: BUILDOPTS+="+gcov" -dist-srpm-gcov: dist-srpm +dist-srpm-%: dist-srpm + @# phony command to force this to be a target and not variable + @FOO=BAR dist-rpms: RPMBUILDOPTS=--target $(MACH) -bb dist-rpms: dist-sources do-rpmbuild @@ -322,8 +328,7 @@ dist-prep: dist-sources do-rpmbuild dist-perf: RPMBUILDOPTS=--without up --without smp --without zfcpdump --without debug --without doc --without headers --without --without doc --without debuginfo --target $(MACH) -bb dist-perf: dist-sources do-rpmbuild -dist-rpm-baseonly: RPMBUILDOPTS=--target $(MACH) --without debug --without debuginfo --without vdso_install --without bpftool --without perf --without tools -bb -dist-rpm-baseonly: dist-sources do-rpmbuild +dist-rpm-%: dist-sources do-rpmbuild # unless you know what you're doing, you don't want to use the next four ones dist-release-finish: setup-source @@ -388,9 +393,25 @@ distg-koji: BUILD_FLAGS ?= $(KOJI_FLAGS) $(TEST_FLAGS) dist-brew dist-koji: dist-%: dist-srpm $* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) $(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm $(OUTPUT_FILE) +dist-brew-%: dist-brew + @# phony command to force this to be a target and not variable + @FOO=BAR + +dist-koji-%: dist-koji + @# phony command to force this to be a target and not variable + @FOO=BAR + distg-brew distg-koji: distg-%: $* $(BUILD_PROFILE) build $(BUILD_FLAGS) $(BUILD_TARGET) "$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)" +distg-brew-%: dist-brew + @# phony command to force this to be a target and not variable + @FOO=BAR + +distg-koji-%: dist-koji + @# phony command to force this to be a target and not variable + @FOO=BAR + .PHONY: $(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec $(REDHAT)/rpm/SOURCES/$(PACKAGE_NAME).spec: @echo "dist-sources" @@ -469,34 +490,30 @@ dist-full-help: @echo 'Building targets:' @echo ' All RPM/SRPM files will be put under the redhat/rpm/ directory.' @echo '' - @echo ' dist-srpm - Create a source RPM and put it into the redhat/rpm/SRPMS/' + @echo ' dist-srpm@ - Create a source RPM and put it into the redhat/rpm/SRPMS/' @echo ' directory. See the dist-brew target for available options.' - @echo ' dist-srpm-gcov - Create a source RPM with gcov enabled and put it into the' - @echo ' redhat/rpm/SRPMS/ directory.' - @echo ' dist-brew - Create a kernel SRPM and then call brew to build the' + @echo ' dist-brew@ - Create a kernel SRPM and then call brew to build the' @echo ' created SRPM. Add BUILDOPTS="+<opt> -<opt> [...]" to' @echo ' enable/disable build options.' @echo ' Available <opt>s and their default values:' \ $$(sed -n -e 's/^%define with_$[^ \t]*$.*\?_without_.*/+\1/p' \ -e 's/^%define with_$[^ \t]*$.*\?_with_.*/-\1/p' kernel.spec.template | \ grep -v 'only$$') | fmt -80 - @echo ' dist-koji - Create a kernel SRPM and then call koji to build the' + @echo ' dist-koji@ - Create a kernel SRPM and then call koji to build the' @echo ' created SRPM. See the dist-brew target for available' @echo ' options.' - @echo ' distg-brew - Pass HEAD of the current git branch to brew to build an' + @echo ' distg-brew@ - Pass HEAD of the current git branch to brew to build an' @echo ' RPM set. Do not forget to push to the remote repository' @echo ' first. Preceed make command by RHGITCOMMIT=<commitID>' @echo ' specify commit ID to use.' @echo ' To set the remote repo, invoke:' @echo ' git config rhg.url git://<repo_path>' - @echo ' distg-koji - Pass HEAD of the current git branch to koji to build an' + @echo ' distg-koji@ - Pass HEAD of the current git branch to koji to build an' @echo ' RPM set. Do not forget to push to the remote repository' @echo ' first. See the distg-brew target for options and' @echo ' configuration.' - @echo ' dist-rpms - Create the binary RPMS for the kernel.' + @echo ' dist-rpms@ - Create the binary RPMS for the kernel.' @echo ' See the dist-brew target for available options.' - @echo ' dist-rpm-baseonly - Create the binary RPMS for the kernel and modules' - @echo ' (no userspace tools or debuginfo).' @echo ' dist-kernel-<type> - Create binary RPMS for a particular kernel type.' @echo ' Available <type>s:'\ $$(sed -n 's/^%define with_$[^ ]*only$.*/\1/p' kernel.spec.template) @@ -524,6 +541,12 @@ dist-full-help: @echo ' dist-rhel-configs - build ELN configs' @echo ' dist-fedora-configs - build Fedora configs' + @echo '' + @echo 'Wildcard targets: [indicated by '@' above]' + @echo ' *-baseonly - builds only the kernel (disables userspace and debuginfo)' + @echo ' - Examples: dist-srpm-baseonly, dist-brew-baseonly' + @echo ' *-gcov - builds a kernel with gcov enabled' + @echo ' - Examples: dist-srpm-gcov, dist-brew-gcov' @echo '' @echo 'kABI targets:' @echo ' dist-kabi - Create kABI stablelist files in redhat/kabi/kabi-rhel*/' -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1444

3 2

[OS-BUILD PATCHv2] Fix binutils breakage
by Don Zickus (via Email Bridge) 15 Aug '24

15 Aug '24

From: Don Zickus <dzickus(a)redhat.com> Fix binutils breakage The binutils package in Rawhide has stricter checks about PIE/PIC code and will start reporting errors if it detects mixing and matching no-PIE with PIE binaries (especially around bpf binaries). Example errors look like: /usr/bin/ld: /tmp/ccL7dkfR.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: failed to set dynamic section sizes: bad value collect2: error: ld returned 1 exit status Fix this by adding more CFLAGS to force PIE/PIC generated binaries to bpf releated selftests, tools and samples. This patch was provided by Carlos O'Donell and understands how it works. I am just the middle man. All -fPIE errors are resolved except for one about libbpf.a. The static version of the library doesn't take CFLAGS so it can't be forced to build with PIE/PIC. This error is ignored by the spec file, so it is ignored by this patch too. Signed-off-by: Don Zickus <dzickus(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 @@ -2769,7 +2769,7 @@ if [ ! -f include/generated/autoconf.h ]; then %{make} %{?_smp_mflags} modules_prepare fi -%{make} %{?_smp_mflags} ARCH=$Arch V=1 M=samples/bpf/ VMLINUX_H="${RPM_VMLINUX_H}" || true +%{make} %{?_smp_mflags} TPROGS_USER_CFLAGS="%{?build_hostcflags}" TPROGS_USER_LDFLAGS="%{?build_hostldflags}" EXTRA_CFLAGS="%{?build_hostcflags}" EXTRA_LDFLAGS="%{?build_hostldflags}" ARCH=$Arch V=1 M=samples/bpf/ VMLINUX_H="${RPM_VMLINUX_H}" || true # Prevent bpf selftests to build bpftool repeatedly: export BPFTOOL=$(pwd)/tools/bpf/bpftool/bpftool @@ -2783,7 +2783,7 @@ pushd tools/testing/selftests force_targets="" %endif -%{make} %{?_smp_mflags} ARCH=$Arch V=1 TARGETS="bpf mm livepatch net net/forwarding net/mptcp netfilter tc-testing memfd drivers/net/bonding" SKIP_TARGETS="" $force_targets INSTALL_PATH=%{buildroot}%{_libexecdir}/kselftests VMLINUX_H="${RPM_VMLINUX_H}" install +%{make} %{?_smp_mflags} USERCFLAGS="%{?build_hostcflags}" USERLDFLAGS="%{?build_hostldflags}" ARCH=$Arch V=1 TARGETS="bpf mm livepatch net net/forwarding net/mptcp netfilter tc-testing memfd drivers/net/bonding" SKIP_TARGETS="" $force_targets INSTALL_PATH=%{buildroot}%{_libexecdir}/kselftests VMLINUX_H="${RPM_VMLINUX_H}" install # 'make install' for bpf is broken and upstream refuses to fix it. # Install the needed files manually. -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2749

4 6

[OS-BUILD PATCHv2 0/0] spec: make sure posttrans script doesn't fail if /boot is non-POSIX
by glb (via Email Bridge) 18 Apr '24

18 Apr '24

From: glb on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3001 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. The Boot Loader Specification recommends that UEFI systems mount the ESP at /boot. Since the ESP is commonly formatted with a non-POSIX file system, symbolic links should not be placed on /boot. ref: https://uapi-group.org/specifications/specs/boot_loader_specification Signed-off-by: Gregory Bartholomew <gregory.lee.bartholomew(a)gmail.com> --- redhat/kernel.spec.template | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

2 6

kernel leftovers in /boot/efi/EFI/Linux/
by Germano Massullo 05 Apr '24

05 Apr '24

Hello, during a dnf update I noticed that /boot/efi was full and the system was not able to update. So I found out in /boot/efi/EFI/Linux/ there are many files belonging to kernel RPMs no longer installed on the system. I am wondering why there are these leftovers. Some of the kernel with .fc39.1 in their name are from RPMs I created to test kernel patches, but they don't have anything special compared to regular Fedora kernel RPMs, since I just rebuilt the package after having added a patch. root@machine:/home/user# eza -lah /boot/efi/EFI/Linux/ Permissions Size User Date Modified Name .rwx------@ 61M root 11 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.4-100.fc39.1.x86_64+debug.efi .rwx------@ 44M root 11 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.4-100.fc39.1.x86_64.efi .rwx------@ 61M root 11 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.4-200.fc39.x86_64+debug.efi .rwx------@ 44M root 11 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.4-200.fc39.x86_64.efi .rwx------@ 62M root 13 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.6-200.fc39.1.x86_64+debug.efi .rwx------@ 44M root 13 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.6-200.fc39.1.x86_64.efi .rwx------@ 61M root 20 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.6-200.fc39.x86_64+debug.efi .rwx------@ 62M root 17 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.6-201.fc39.1.x86_64+debug.efi .rwx------@ 44M root 17 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.6-201.fc39.1.x86_64.efi .rwx------@ 1,2M root 20 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.7-200.fc39.x86_64+debug.efi .rwx------@ 0 root 31 dic 2023 3fca3f6e08d1481a961d4954bff61ddf-6.6.8-200.fc39.x86_64+debug.efi .rwx------@ 0 root 7 gen 00:31 3fca3f6e08d1481a961d4954bff61ddf-6.6.9-200.fc39.x86_64+debug.efi .rwx------@ 0 root 16 gen 11:04 3fca3f6e08d1481a961d4954bff61ddf-6.6.11-200.fc39.x86_64+debug.efi .rwx------@ 0 root 24 gen 20:44 3fca3f6e08d1481a961d4954bff61ddf-6.6.12-200.fc39.x86_64+debug.efi .rwx------@ 0 root 26 gen 23:15 3fca3f6e08d1481a961d4954bff61ddf-6.6.13-200.fc39.x86_64+debug.efi .rwx------@ 0 root 4 feb 17:50 3fca3f6e08d1481a961d4954bff61ddf-6.6.14-200.fc39.x86_64+debug.efi root@machine:/home/user# rpm -q kernel kernel-6.6.12-200.fc39.x86_64 kernel-6.6.13-200.fc39.x86_64 kernel-6.6.14-200.fc39.x86_64

3 14

[OS-BUILD PATCHv12 0/2] redhat/kernel.spec: add uki_addons to create UKI kernel cmdline addons
by Emanuele Giuseppe Esposito (via Email Bridge) 03 Apr '24

03 Apr '24

From: Emanuele Giuseppe Esposito on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2917 We want to enable kernel.spec to optionally ship UKI addons defined in a common config file in redhat folder. The folder redhat/addons will contain all addons configs specifying the UKI kernel cmdline addons to be created in the next build. An addon config is simply a .addon plain text file, where any line is taken as kernel cmdline, except for the ones starting with '#', which will be automatically ignored. redhat/scripts/uki_addons.py will take care of parsing all configs and folders in redhat/addons and call 'ukify' to create the actual addons. The output addon filename will be a concatenation of all folders in redhat/addons that are part of the addon config path. For example, an addon config redhat/addons/1/2/3/test.addon will result in generating redhat/addons_output/1-2-3-test.addon.efi. It is also possible to add .sbat to all the generated addons, by populating redhat/addons/sbat/sbat.conf. Syntax is same as the addons config. At build time, Makefile will create a tar.gz archive (addons.tar.gz) containing all the files in redhat/addons. It will then passed to the kernel specfile that will extract the addons from it and generate the UKI kernel cmdline addons. As an example of this feature, add the fips addon to optionally enable fips (https://issues.redhat.com/browse/RHEL-23049) --- redhat/addons/virt/common/fips.addon | 2 + redhat/scripts/uki_addons.py | 157 +++++++++++++++++++++++++++++++++++ redhat/Makefile | 3 + redhat/kernel.spec.template | 44 +++++++++ 4 files changed, 206 insertions(+), 0 deletions(-)

2 11

[OS-BUILD PATCHv2 0/6] secure boot signing updates
by Jan Stancek (via Email Bridge) 02 Apr '24

02 Apr '24

From: Jan Stancek on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2849 Forward port secure boot signing changes from c9s to ARK. eln scratch: https://koji.fedoraproject.org/koji/taskinfo?taskID=111509830 rawhide scratch: https://koji.fedoraproject.org/koji/taskinfo?taskID=111494146 Signed-off-by: Jan Stancek <jstancek(a)redhat.com> --- redhat/keys/redhatsecureboot003.cer | Bin redhat/keys/redhatsecureboot301.cer | Bin redhat/keys/redhatsecureboot401.cer | Bin redhat/keys/redhatsecurebootca1.cer | Bin redhat/keys/redhatsecurebootca2.cer | Bin redhat/keys/redhatsecurebootca4.cer | Bin redhat/keys/secureboot_ppc.cer | Bin redhat/keys/secureboot_s390.cer | Bin redhat/Makefile | 7 +- redhat/kernel.spec.template | 113 +++++++++++++++-------------------- 10 files changed, 51 insertions(+), 69 deletions(-)

2 9

✅ PASS (MISSED 9 of 113): Test report for 6.7.11-200.fc39 (kernel-fedora)
by cki-project＠redhat.com 28 Mar '24

28 Mar '24

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: 115517138 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/137766 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: Filesystem - NFS Connectathon [x86_64] Tests that were not ran because of internal issues: Boot test [aarch64] CKI/restraint [aarch64] machineinfo [aarch64] Reboot test [x86_64, aarch64] SELinux Custom Module Setup [aarch64] selinux-policy: serge-testsuite [aarch64] stress: stress-ng - cpu-cache [x86_64] stress: stress-ng - memory [x86_64] 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 PATCH] redhat/configs: build in Tegra210 SPI driver
by Mark Salter (via Email Bridge) 27 Mar '24

27 Mar '24

From: Mark Salter <msalter(a)redhat.com> redhat/configs: build in Tegra210 SPI driver Nvidia Grace has a TPM attached to this SPI controller and it does not get loaded in time for IMA. So build in SPI driver so that the TPM loads in time for IMA. Signed-off-by: Mark Salter <msalter(a)redhat.com> diff --git a/redhat/configs/common/generic/arm/aarch64/CONFIG_SPI_TEGRA210_QUAD b/redhat/configs/common/generic/arm/aarch64/CONFIG_SPI_TEGRA210_QUAD index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/arm/aarch64/CONFIG_SPI_TEGRA210_QUAD +++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_SPI_TEGRA210_QUAD @@ -1 +1 @@ -CONFIG_SPI_TEGRA210_QUAD=m +CONFIG_SPI_TEGRA210_QUAD=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3050

1 0

[OS-BUILD PATCH] redhat/configs: Enable CONFIG_AMDTEE for x86
by David Arcari (via Email Bridge) 27 Mar '24

27 Mar '24

From: David Arcari <darcari(a)redhat.com> redhat/configs: Enable CONFIG_AMDTEE for x86 This config is required in order for CONFIG_AMD_PMF to be enabled. Signed-off-by: David Arcari <darcari(a)redhat.com> diff --git a/redhat/configs/common/generic/x86/CONFIG_AMDTEE b/redhat/configs/common/generic/x86/CONFIG_AMDTEE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/x86/CONFIG_AMDTEE @@ -0,0 +1 @@ +CONFIG_AMDTEE=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3049

2 1

[OS-BUILD PATCH] redhat/configs: aarch64: Enable ARM_FFA driver
by Mark Salter (via Email Bridge) 27 Mar '24

27 Mar '24

From: Mark Salter <msalter(a)redhat.com> redhat/configs: aarch64: Enable ARM_FFA driver Some newer platforms are making use of the Arm Firmaware Framework, so lets enable it for RHEL also. Signed-off-by: Mark Salter <msalter(a)redhat.com> diff --git a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT rename from redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT rename to redhat/configs/common/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT +++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT diff --git a/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT b/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARM_FFA_TRANSPORT +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_ARM_FFA_TRANSPORT is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3048

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel March 2024