November 2020 - kernel - Fedora Mailing-Lists

[OS-BUILD PATCH] [redhat] New configs in net/xfrm

by GitLab Bridge on behalf of jeremycline

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> 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_XFRM_USER_COMPAT: Transformation(XFRM) user configuration interface like IPsec used by compatible Linux applications. If unsure, say N. Symbol: XFRM_USER_COMPAT [=n] Type : tristate Defined at net/xfrm/Kconfig:31 Prompt: Compatible ABI support Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y] Location: -> Networking support (NET [=y]) -> Networking options -> Transformation user configuration interface (XFRM_USER [=y]) Selects: WANT_COMPAT_NETLINK_MESSAGES [=n] --- Cc: Jiri Benc <jbenc(a)redhat.com> Cc: Marcelo Leitner <mleitner(a)redhat.com> Cc: Davide Caratti <dcaratti(a)redhat.com> Cc: Eric Garver <egarver(a)redhat.com> Cc: Flavio Leitner <fbl(a)redhat.com> Cc: Florian Westphal <fwestpha(a)redhat.com> Cc: Guillaume Nault <gnault(a)redhat.com> Cc: Hangbin Liu <haliu(a)redhat.com> Cc: Ivan Vecera <ivecera(a)redhat.com> Cc: Jarod Wilson <jarod(a)redhat.com> Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com> Cc: Paolo Abeni <pabeni(a)redhat.com> Cc: Phil Sutter <psutter(a)redhat.com> Cc: Sabrina Dubroca <sdubroca(a)redhat.com> Cc: Stefano Brivio <sbrivio(a)redhat.com> Cc: Xin Long <lxin(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_XFRM_USER_COMPAT | 1 + .../generic/CONFIG_XFRM_USER_COMPAT | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT diff --git a/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT new file mode 100644 index 000000000000..798d10e8e93e --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT @@ -0,0 +1 @@ +# CONFIG_XFRM_USER_COMPAT is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT deleted file mode 100644 index 7941fd360e9b..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_XFRM_USER_COMPAT: -# -# Transformation(XFRM) user configuration interface like IPsec -# used by compatible Linux applications. -# -# If unsure, say N. -# -# Symbol: XFRM_USER_COMPAT [=n] -# Type : tristate -# Defined at net/xfrm/Kconfig:31 -# Prompt: Compatible ABI support -# Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y] -# Location: -# -> Networking support (NET [=y]) -# -> Networking options -# -> Transformation user configuration interface (XFRM_USER [=y]) -# Selects: WANT_COMPAT_NETLINK_MESSAGES [=n] -# -# -# -# CONFIG_XFRM_USER_COMPAT is not set -- GitLab

3 years, 4 months

4
5
0 / 0

Reporting kernel building docs problems?

by Bastien Nocera

Hey, A couple of months ago I filed bugs about the kernel-cki build process and some problems I encountered: https://gitlab.com/cki-project/kernel-ark/-/issues Today, I wanted to build a test kernel for a Fedora user with an additional custom patch, and couldn't find much interesting or up-to-date docs about it. This is outdated: https://fedoraproject.org/wiki/Building_a_custom_kernel#Building_a_Kernel... and kernel.spec still mentions "make" targets. Are those docs going to get updated, or are new docs available that should deprecate and replace those? Cheers --- Bastien Nocera he/him/his

3 years, 4 months

3
2
0 / 0

✅ PASS: Test report for kernel 5.9.10-100.fc32 (fedora-32)

by CKI Project

Hello jforbes, We ran automated tests on the following kernel build: Kernel package: kernel-5.9.10-100.fc32 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=56135479 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre... 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: ✅ Boot test ✅ stress: stress-ng 🚧 ❌ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ❌ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 ❌ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity x86_64: Host 1: ⏱ Boot test ⏱ stress: stress-ng ⏱ xfstests - ext4 ⏱ xfstests - xfs ⏱ xfstests - btrfs ⏱ Storage blktests ⏱ Storage block - filesystem fio test ⏱ Storage block - queue scheduler test ⏱ Storage nvme - tcp ⏱ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test 🚧 ✅ kdump - sysrq-c Host 3: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity 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 ⏱.

3 years, 4 months

1
0
0 / 0

Fwd: [OS-BUILD PATCHv2 0/4] Fix bug 1882854

by Paulo Edgar Castro

On 12/11/2020 19:28, Justin Forbes wrote: > That said, I also do not particularly like copying all of tools > either. I would much rather trim this down to exactly what is needed. > Remember, users with kernel-devel installed are likely to have 3 > copies installed at any given time. Is the latest https://gitlab.com/cki-project/kernel-ark/-/merge_requests/761/diffs?diff... better enough for a thumbs up ? Regards, PECastro

3 years, 5 months

1
0
0 / 0

[OS-BUILD PATCH] Temporarily backout parallel xz script

by GitLab Bridge on behalf of jmflinuxtx

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> For quite some time, the parallel_xz.sh script has been hanging up builds in koji. While it may be a benefit to get this fixed, it is much better to back that change out in the short term. This reverts us to the way that Fedora used to compress the modules. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- redhat/kernel.spec.template | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index 4d16c0005536..34e32e982a49 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -83,6 +83,8 @@ Summary: The Linux kernel %if %{zipmodules} %global zipsed -e 's/\.ko$/\.ko.xz/' +# for parallel xz processes, replace with 1 to go back to single process +%global zcpu `nproc --all` %endif %%BUILDID%% @@ -2063,7 +2065,7 @@ find Documentation -type d | xargs chmod u+w fi \ fi \ if [ "%{zipmodules}" -eq "1" ]; then \ - find $RPM_BUILD_ROOT/lib/modules/ -type f -name '*.ko' | %{SOURCE79} %{?_smp_mflags}; \ + find $RPM_BUILD_ROOT/lib/modules/ -type f -name '*.ko' | xargs -P%{zcpu} xz; \ fi \ %{nil} -- GitLab

3 years, 5 months

3
2
0 / 0

❌ FAIL: Test report for kernel 5.9.9-100.fc32 (fedora-32)

by CKI Project

Hello jforbes, We ran automated tests on the following kernel build: Kernel package: kernel-5.9.9-100.fc32 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=55878390 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: x86_64: ❌ LTP All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre... 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: ✅ Boot test ✅ stress: stress-ng 🚧 ❌ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity ppc64le: Host 1: ✅ Boot test 🚧 ❌ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity s390x: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 ❌ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 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 ⚡⚡⚡ stress: stress-ng 🚧 ⚡⚡⚡ xfstests - ext4 🚧 ⚡⚡⚡ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test 🚧 ❌ kdump - sysrq-c 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 ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 4: ✅ Boot test ✅ ACPI table test ❌ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity 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 ⏱.

3 years, 5 months

1
0
0 / 0

[OS-BUILD PATCH] [redhat] New configs in drivers/acpi

by GitLab Bridge on behalf of jeremycline

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> 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. --- Cc: Al Stone <ahs3(a)redhat.com> Cc: Lenny Szubowicz <lszubowi(a)redhat.com> Cc: Prarit Bhargava <prarit(a)redhat.com> Cc: David Arcari <darcari(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_ACPI_TABLE_UPGRADE | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ACPI_TABLE_UPGRADE diff --git a/redhat/configs/common/generic/CONFIG_ACPI_TABLE_UPGRADE b/redhat/configs/common/generic/CONFIG_ACPI_TABLE_UPGRADE new file mode 100644 index 000000000000..e69de29bb2d1 -- GitLab

3 years, 5 months

4
3
0 / 0

USB-C power patch to cherry-pick

by Bastien Nocera

Hey, This now upstreamed patch would be quite useful to have in stable versions of Fedora, it fixes problems with the AC/battery status not reflecting reality on some USB-C powered machines: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit... upower bug: https://gitlab.freedesktop.org/upower/upower/-/issues/126 Let me know if you need anymore information, or prefer that I create an MR. --- Bastien Nocera he/him/his

3 years, 5 months

2
2
0 / 0

Enabling CONFIG_ACPI_TABLE_UPGRADE in Fedora kernels

by Hans de Goede

Hi All, I believe $subject has been discussed before but I would like to see us reconsider this. I know that the general rule of thumb is that DSDTs should not be overriden and instead the kernel should be made to "just work" with existing DSDTs even if they are buggy. And as someone who does a lot of ACPI related bug-fixing in the upstream kernel, I completely agree. IIRC this was the main argument against enabling CONFIG_ACPI_TABLE_UPGRADE, but even with it enabled actually using this is far from easy, so I'm NOT worried that this will cause uses to do DSDT overrides to paper over bugs which we really should fix otherwise. But sometimes being able to override the DSDT is still useful: 1. When I'm helping users to get various hardware issues fixed sometimes it is useful to given them a DSDT override changing e.g. the bus-speed for an I2C bus, or changing the type of an IRQ from level to edge, etc. 2. Unfortunately there is a small number of DSDT bugs which the kernel simply cannot be fixed to handle. I know at least 2 examples of this: Example a. The Onda v975w ACPI battery code has a bug where the full capacity always reports 0. This is a very straight forward error in the DSDT, not a case of using some wiggle room in the ACPI spec (expecting certain behavior which only Windows shows). This is simply a DSDT bug. The code might just a well say "return 0" Example b. The Acer Switch sw5-012 is completely missing the ACPI Device (PWM0) section declaring the PWM controller which is used for controlling the backlight of the LCD. This leads to non working brightness control and also to much to high energy drain while suspended. For both these cases having CONFIG_ACPI_TABLE_UPGRADE=y would be very helpful. The only downside would be that this is not compatible with secureboot. So if not done upstream already then we must tie this to the kernel-lockdown stuff and disallow it when lockdown mode is active. I can try to write a patch for this if necessary. Regards, Hans

3 years, 5 months

5
5
0 / 0

enrollment to the mailing list

by Claudio ＠ Gmail

Hi, Please add my email (cchinicz(a)gmail.com) to your mailing list. Thanks, Claudio

3 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel November 2020