kernel July 2021

kernel@lists.fedoraproject.org

14 participants
77 discussions

[OS-BUILD PATCHv2] [redhat] Enable CONFIG_RANDOM_TRUST_CPU for all the arches
by Vladis Dronov (via Email Bridge) 31 Jul '21

31 Jul '21

From: Vladis Dronov <vdronov(a)redhat.com> [redhat] Enable CONFIG_RANDOM_TRUST_CPU for all the arches Many modern cloud instance types have hardware with RDRAND, but the RHEL-9 still do not use it. Enable CONFIG_RANDOM_TRUST_CPU the same way as in the RHEL-8 and Fedora and add ARM too. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976877 Signed-off-by: Vladis Dronov <vdronov(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU +++ b/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU @@ -1 +1 @@ -# CONFIG_RANDOM_TRUST_CPU is not set +CONFIG_RANDOM_TRUST_CPU=y diff --git a/redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU +++ /dev/null @@ -1 +0,0 @@ -CONFIG_RANDOM_TRUST_CPU=y diff --git a/redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU +++ /dev/null @@ -1 +0,0 @@ -CONFIG_RANDOM_TRUST_CPU=y diff --git a/redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU +++ /dev/null @@ -1 +0,0 @@ -CONFIG_RANDOM_TRUST_CPU=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1287

4 4

[OS-BUILD PATCH] x86: configs: Enable CONFIG_TEST_FPU for debug kernels
by Vitaly Kuznetsov (via Email Bridge) 30 Jul '21

30 Jul '21

From: Vitaly Kuznetsov <vkuznets(a)redhat.com> x86: configs: Enable CONFIG_TEST_FPU for debug kernels Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1988384 CONFIG_TEST_FPU selftest is needed to test in-kernel FPU usage. Signed-off-by: Vitaly Kuznetsov <vkuznets(a)redhat.com> diff --git a/redhat/configs/common/debug/CONFIG_TEST_FPU b/redhat/configs/common/debug/CONFIG_TEST_FPU new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/debug/CONFIG_TEST_FPU @@ -0,0 +1 @@ +CONFIG_TEST_FPU=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1286

4 3

[OS-BUILD PATCH] [redhat] Enable CONFIG_RANDOM_TRUST_CPU for all arches but aarch64
by Vladis Dronov (via Email Bridge) 30 Jul '21

30 Jul '21

From: Vladis Dronov <vdronov(a)redhat.com> [redhat] Enable CONFIG_RANDOM_TRUST_CPU for all arches but aarch64 Many modern cloud instance types have hardware with RDRAND, but the RHEL-9 still do not use it. Enable CONFIG_RANDOM_TRUST_CPU the same way as in the RHEL-8 and Fedora. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976877 Signed-off-by: Vladis Dronov <vdronov(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/common/generic/CONFIG_RANDOM_TRUST_CPU +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_RANDOM_TRUST_CPU is not set diff --git a/redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/common/generic/powerpc/CONFIG_RANDOM_TRUST_CPU rename from redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU rename to redhat/configs/common/generic/powerpc/CONFIG_RANDOM_TRUST_CPU index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/powerpc/CONFIG_RANDOM_TRUST_CPU +++ b/redhat/configs/common/generic/powerpc/CONFIG_RANDOM_TRUST_CPU diff --git a/redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/common/generic/s390x/CONFIG_RANDOM_TRUST_CPU rename from redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU rename to redhat/configs/common/generic/s390x/CONFIG_RANDOM_TRUST_CPU index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/s390x/CONFIG_RANDOM_TRUST_CPU +++ b/redhat/configs/common/generic/s390x/CONFIG_RANDOM_TRUST_CPU diff --git a/redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU b/redhat/configs/common/generic/x86/CONFIG_RANDOM_TRUST_CPU rename from redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU rename to redhat/configs/common/generic/x86/CONFIG_RANDOM_TRUST_CPU index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/x86/CONFIG_RANDOM_TRUST_CPU +++ b/redhat/configs/common/generic/x86/CONFIG_RANDOM_TRUST_CPU -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1287

2 2

[OS-BUILD PATCH 0/0] [redhat] New configs in drivers/scsi
by CKI Gitlab (via Email Bridge) 30 Jul '21

30 Jul '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1218 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. CONFIG_FC_APPID: If you say Y here, it enables the support to track FC I/O traffic over fabric. It enables the Fabric and the storage targets to identify, monitor, and handle FC traffic based on VM tags by inserting application specific identification into the FC frame. Symbol: FC_APPID [=y] Type : bool Defined at drivers/scsi/Kconfig:238 Prompt: Enable support to track FC I/O Traffic Depends on: BLOCK [=y] && BLK_CGROUP [=y] && SCSI [=y] Location: -> Device Drivers -> SCSI device support -> SCSI Transports Selects: BLK_CGROUP_FC_APPID [=y] --- CONFIG_SCSI_EFCT: The efct driver provides enhanced SCSI Target Mode support for specific SLI-4 adapters. Symbol: SCSI_EFCT [=n] Type : tristate Defined at drivers/scsi/elx/Kconfig:1 Prompt: Emulex Fibre Channel Target Depends on: SCSI_LOWLEVEL [=y] && PCI [=y] && SCSI [=y] && TARGET_CORE [=m] && SCSI_FC_ATTRS [=m] Location: -> Device Drivers -> SCSI device support -> SCSI low-level drivers (SCSI_LOWLEVEL [=y]) Selects: CRC_T10DIF [=y] --- CONFIG_SCSI_MPI3MR: MPI3 based Storage & RAID Controllers Driver. Symbol: SCSI_MPI3MR [=n] Type : tristate Defined at drivers/scsi/mpi3mr/Kconfig:3 Prompt: Broadcom MPI3 Storage Controller Device Driver Depends on: SCSI_LOWLEVEL [=y] && PCI [=y] && SCSI [=y] Location: -> Device Drivers -> SCSI device support -> SCSI low-level drivers (SCSI_LOWLEVEL [=y]) --- Cc: "Ewan D. Milne" <emilne(a)redhat.com> Cc: Tomas Henzl <thenzl(a)redhat.com> Cc: Maurizio Lombardi <mlombard(a)redhat.com> Cc: Chris Leech <cleech(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_FC_APPID | 1 + redhat/configs/common/generic/CONFIG_SCSI_EFCT | 1 + redhat/configs/common/generic/CONFIG_SCSI_MPI3MR | 1 + redhat/configs/pending-common/generic/CONFIG_FC_APPID | 22 ---------------- redhat/configs/pending-common/generic/CONFIG_SCSI_EFCT | 19 ------------- redhat/configs/pending-common/generic/CONFIG_SCSI_MPI3MR | 17 ------------ 6 files changed, 3 insertions(+), 58 deletions(-)

2 1

❌ FAIL: Test report for kernel 5.13.6-200.fc34 (fedora-34)
by CKI Project 30 Jul '21

30 Jul '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.13.6-200.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=72845736 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 💥 xarray-idr-radixtree-test All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… 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 ⚡⚡⚡ 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 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ storage: software RAID testing 🚧 💥 stress: stress-ng Host 3: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP ✅ 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: ⚡ 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 ⚡⚡⚡ 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 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 3: ✅ Boot test ✅ Reboot test ❌ LTP ✅ 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 🚧 ✅ Storage nvme - tcp 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ Reboot test ✅ LTP ✅ 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: ⚡ 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 ⚡⚡⚡ 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 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng 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 ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ 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 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 ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ 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 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 ⏱.

1 0

[OS-BUILD PATCH] kernel.spec: fix build of samples/bpf
by Jiri Benc (via Email Bridge) 29 Jul '21

29 Jul '21

From: Jiri Benc <jbenc(a)redhat.com> kernel.spec: fix build of samples/bpf Due to some change of the kernel makefiles, "samples/bpf" does not work anymore as a make target. Use M= instead. Signed-off-by: Jiri Benc <jbenc(a)redhat.com> 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 @@ -2234,7 +2234,7 @@ popd # in the source tree. We installed them previously to $RPM_BUILD_ROOT/usr # but there's no way to tell the Makefile to take them from there. %{make} %{?_smp_mflags} headers_install -%{make} %{?_smp_mflags} ARCH=$Arch V=1 samples/bpf/ +%{make} %{?_smp_mflags} ARCH=$Arch V=1 M=samples/bpf/ # Prevent bpf selftests to build bpftool repeatedly: export BPFTOOL=$(pwd)/tools/bpf/bpftool/bpftool -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1285

5 4

[OS-BUILD PATCH] Enable OSNOISE_TRACER and TIMERLAT_TRACER
by Jerome Marchand (via Email Bridge) 29 Jul '21

29 Jul '21

From: Jerome Marchand <jmarchan(a)redhat.com> Enable OSNOISE_TRACER and TIMERLAT_TRACER Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1979379 There is actually a need for these tracers. Signed-off-by: Jerome Marchand <jmarchan(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_OSNOISE_TRACER b/redhat/configs/common/generic/CONFIG_OSNOISE_TRACER index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_OSNOISE_TRACER +++ b/redhat/configs/common/generic/CONFIG_OSNOISE_TRACER @@ -1 +1 @@ -# CONFIG_OSNOISE_TRACER is not set +CONFIG_OSNOISE_TRACER=y diff --git a/redhat/configs/common/generic/CONFIG_TIMERLAT_TRACER b/redhat/configs/common/generic/CONFIG_TIMERLAT_TRACER index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_TIMERLAT_TRACER +++ b/redhat/configs/common/generic/CONFIG_TIMERLAT_TRACER @@ -1 +1 @@ -# CONFIG_TIMERLAT_TRACER is not set +CONFIG_TIMERLAT_TRACER=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1281

4 6

[OS-BUILD PATCH] Revert "Drop that for now"
by Herton R. Krzesinski (via Email Bridge) 28 Jul '21

28 Jul '21

From: Herton R. Krzesinski <herton(a)redhat.com> Revert "Drop that for now" This reverts commit 1f80f9253eb2b6a5f63e2053d8e54062791bcff7. Unfortunately the commit message was cryptic on this one, but it was done probably to handle the same case as was already done with upstream commit 6f303d60534c4 ("gcc-9: silence 'address-of-packed-member' warning"). Thus the addition of -Wno-address-of-packed-member was already done in upstream commit above, we don't need to add it again in the initial list of KBUILD_CFLAGS. I manually verified a random built file with "make KBUILD_VERBOSE=1 (...)" and checked that we don't have anymore -Wno-address-of-packed-member being passed two times to gcc. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff --git a/Makefile b/Makefile index blahblah..blahblah 100644 --- a/Makefile +++ b/Makefile @@ -512,7 +512,6 @@ KBUILD_AFLAGS := -D__ASSEMBLY__ -fno-PIE KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \ -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE \ -Werror=implicit-function-declaration -Werror=implicit-int \ - -Wno-address-of-packed-member \ -Werror=return-type -Wno-format-security \ -std=gnu89 KBUILD_CPPFLAGS := -D__KERNEL__ -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1283

3 2

[OS-BUILD PATCH] rpmspec: switch iio and gpio tools to use tools_make
by Herton R. Krzesinski (via Email Bridge) 27 Jul '21

27 Jul '21

From: Herton R. Krzesinski <herton(a)redhat.com> rpmspec: switch iio and gpio tools to use tools_make Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1956988 In the past, some of the kernel tools Makefiles didn't allow the override of CFLAGS, which made them compiled without stack protector and without position independent code. This triggers CI failures in RHEL with annocheck. However, since upstream commits 4ccc98a48958da9f89beb71c66a4e05468727951 (tools gpio: Allow overriding CFLAGS) and 572974610273d58b35d6632eb3a07b6f048c5b89 (tools iio: Override CFLAGS assignments), we can override the compiler flags, so just convert the build of iio and gpio tools to use tools_make macro as other tools, which passes the correct CFLAGS. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> 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 @@ -2206,12 +2206,10 @@ pushd tools/thermal/tmon/ %{tools_make} popd pushd tools/iio/ -# Needs to be fixed to pick up CFLAGS -%{__make} +%{tools_make} popd pushd tools/gpio/ -# Needs to be fixed to pick up CFLAGS -%{__make} +%{tools_make} popd # build VM tools pushd tools/vm/ @@ -2466,10 +2464,10 @@ pushd tools/thermal/tmon %{tools_make} INSTALL_ROOT=%{buildroot} install popd pushd tools/iio -%{__make} DESTDIR=%{buildroot} install +%{tools_make} DESTDIR=%{buildroot} install popd pushd tools/gpio -%{__make} DESTDIR=%{buildroot} install +%{tools_make} DESTDIR=%{buildroot} install popd install -m644 -D %{SOURCE2002} %{buildroot}%{_sysconfdir}/logrotate.d/kvm_stat pushd tools/kvm/kvm_stat -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1276

3 2

[OS-BUILD PATCH] configs/process_configs.sh: Handle config items with no help text
by Patrick Talbert (via Email Bridge) 26 Jul '21

26 Jul '21

From: Patrick Talbert <ptalbert(a)redhat.com> configs/process_configs.sh: Handle config items with no help text The current config scripts logic expects the helpnewconfig output for each item to begin with the full config item name followed by a colon. But if a config item has no help text then the helpnewconfig output does not follow this format. Fix this by adjusting the process_configs.sh and gen_config_patches.sh awk scripts so they get the config item name from the Symbol: line which is always present in helpnewconfig output Signed-off-by: Patrick Talbert <ptalbert(a)redhat.com> diff --git a/redhat/configs/process_configs.sh b/redhat/configs/process_configs.sh index blahblah..blahblah 100755 --- a/redhat/configs/process_configs.sh +++ b/redhat/configs/process_configs.sh @@ -145,9 +145,9 @@ parsenewconfigs() BEGIN { inpatch=0; outfile="none"; symbol="none"; } - /^CONFIG_.*:$/ { - split($0, a, ":"); - symbol=a[1]; + /^Symbol: .*$/ { + split($0, a, " "); + symbol="CONFIG_"a[2]; outfile=BASE "/fake_"symbol } /-----/ { diff --git a/redhat/gen_config_patches.sh b/redhat/gen_config_patches.sh index blahblah..blahblah 100755 --- a/redhat/gen_config_patches.sh +++ b/redhat/gen_config_patches.sh @@ -83,10 +83,9 @@ while read -r line; do print config >> subsystem_path; next; } - /^# CONFIG_.*:/ { - split($0, a); - split(a[2], b, ":"); - config=b[1]; + /^# Symbol: .*/ { + split($0, a, " "); + config="CONFIG_"a[3]; #print config; } ' "$line" -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1277

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel July 2021