kernel February 2021

kernel@lists.fedoraproject.org

24 participants
153 discussions

[OS-BUILD PATCH 0/7] Move all x86 legacy input options to that architecture
by GitLab Bridge on behalf of pbrobinson 09 Mar '21

09 Mar '21

From: pbrobinson on gitlab.com None of the non x86 architectures support PS2, AT keyboards, i8042 controllers and related bits. This cleans up a bunch of those options as well as syncing some of the Fedora options on non x86 to be the same as ARK by moving the ARK bits to generic. Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>

5 16

[OS-BUILD PATCH] Disable bluetooth highspeed by default
by GitLab Bridge on behalf of pbrobinson 09 Mar '21

09 Mar '21

From: Peter Robinson <pbrobinson(a)gmail.com> Upstream has disabled BT_HS by disabled because it wasn't widely adopted. It's also been referenced upstream by BleedingTooth vulnerability: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-0… Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> --- redhat/configs/common/generic/CONFIG_BT_HS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redhat/configs/common/generic/CONFIG_BT_HS b/redhat/configs/common/generic/CONFIG_BT_HS index e0151a2e9e0d..fbbd6bcf002f 100644 --- a/redhat/configs/common/generic/CONFIG_BT_HS +++ b/redhat/configs/common/generic/CONFIG_BT_HS @@ -1 +1 @@ -CONFIG_BT_HS=y +# CONFIG_BT_HS is not set -- GitLab

4 3

[OS-BUILD PATCH 0/8] 5.11 general can cleanup
by GitLab Bridge on behalf of pbrobinson 08 Mar '21

08 Mar '21

From: pbrobinson on gitlab.com Cleanups to CAN for the enabled core CAN support and devices across common/ark/fedora. Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com>

4 11

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by CKI Gitlab (via Email Bridge) 05 Mar '21

05 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in lib/Kconfig.debug 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_DEBUG_IRQFLAGS: Enables checks for potentially unsafe enabling or disabling of interrupts, such as calling raw_local_irq_restore() when interrupts are enabled. Symbol: DEBUG_IRQFLAGS [=n] Type : bool Defined at lib/Kconfig.debug:1427 Prompt: Debug IRQ flag manipulation Location: -> Kernel hacking Selected by [n]: - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n] --- Cc: Prarit Bhargava <prarit(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS @@ -0,0 +1 @@ +# CONFIG_DEBUG_IRQFLAGS is not set diff a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_DEBUG_IRQFLAGS: -# -# Enables checks for potentially unsafe enabling or disabling of -# interrupts, such as calling raw_local_irq_restore() when interrupts -# are enabled. -# -# Symbol: DEBUG_IRQFLAGS [=n] -# Type : bool -# Defined at lib/Kconfig.debug:1427 -# Prompt: Debug IRQ flag manipulation -# Location: -# -> Kernel hacking -# Selected by [n]: -# - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n] -# -# -# -# CONFIG_DEBUG_IRQFLAGS is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/912

3 2

Re: Building custom kernels
by Julian Sikorski 02 Mar '21

02 Mar '21

W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: > Hi, > > I am trying to test some Renoir s2idle patches [1]. It appears that > Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What > I tried is adding the patches to the fedora-5.11 branch and running make > dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: > > Processing > /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config > ... Error: Mismatches found in configuration files > Found CONFIG_INIT_STACK_NONE=y after generation, had > CONFIG_INIT_STACK_NONE=is not set in Source tree > make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 > > Is this expected? Is there a better way of testing patches on Fedora > kernels? Thanks for the help in advance. > > Best regards, > Julian > > [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 > [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian

2 2

[OS-BUILD PATCH 0/4] Drop stale pinephone patches
by Herton Krzesinski (via Email Bridge) 01 Mar '21

01 Mar '21

From: Herton Krzesinski on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/925 Seems a while ago PinePhone patches not yet upstreamed where added. However, some of them were reworked/dropped in its way upstream, and this looks the final version that went in: https://patchwork.freedesktop.org/series/79025/ It got merged upstream through these commits: 5f5df8b4253f12dbc0b9e328b3334ce28c16fc08^..c8a753484066a6382d2539d3dca14 28164a682bf a6a22f82c90dab8966fc07bd7e798a0680803995^..60f2de5ffbf0ed7c0d9789bcc1968 84427e8cff5 However, we still have some stale commits/patches that were not dropped with the upstream merge. Remove them now.

5 13

Dealing with i915 graphics issues reported by multipe people in kernel >= 5.10.9
by Hans de Goede 01 Mar '21

01 Mar '21

Hi, I've been working with various reporters to try and get the sometimes severe gfx glitches which people are seeing with kernel >= 5.10.9 resolved, see the following bugs: 1843274 - i915 GPU Hang with kernel 5.7 on Haswell (Acer C720P Chromebook) 1925346 - Screen glitches after updating to Kernel 5.10.10 1925903 - Flickering UI elements, screen instability (Wayland) 1931065 - Frequent i915 hangs I've written 2 patches 2 address this and asked users to test Fedora-kernel scratch-builds with those patches added. The first patch is i915-revert.patch, this reverts 3 troublesome commits which were first added in 5.10.9 these commit change the i915 mitigations for a year old i915 CVE which IIRC was mostly about data leaking from a previous GPU context to the next. These patches enable these mitigations on more GPU models, where they were previously disabled because they were causing issues... Reporters have reported a 100% success-rate in getting rid of the gfx issues with these 3 reverts. The second patch is i915-fixes.patch, this cherry-picks 3 patches from -next instead (these were suggested by i915 upstream) and this also helps for most users, but some users still report some rendering artifacts (but overall things are much better). Upstream has gone silent on the issue of there still being rendering artifacts with the 3 cherry-picked fixes unfortunately. Given that we are getting more and more bug-reports about this I think that we should be do something about this downstream. Upstream seams to be aiming for fixing things, rather then reverting, so going with i915-fixes.patch will stay the closest to what I expect to land in 5.10.y and 5.11.y at some point. Regards, Hans

3 9

[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 27 Feb '21

27 Feb '21

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_CMDLINE: On some platforms, there is currently no way for the boot loader to pass arguments to the kernel. For these platforms, you can supply some command-line options at build time by entering them here. In most cases you will need to specify the root device here. Symbol: CMDLINE [=] Type : string Defined at arch/powerpc/Kconfig:882 Prompt: Initial kernel command string Location: -> Kernel options --- CONFIG_PPC_QUEUED_SPINLOCKS: Say Y here to use queued spinlocks which give better scalability and fairness on large SMP and NUMA systems without harming single threaded performance. This option is currently experimental, the code is more complex and less tested so it defaults to "N" for the moment. If unsure, say "N". Symbol: PPC_QUEUED_SPINLOCKS [=n] Type : bool Defined at arch/powerpc/Kconfig:497 Prompt: Queued spinlocks Depends on: SMP [=y] Location: -> Kernel options --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_CMDLINE | 1 + .../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 1 + .../pending-common/generic/CONFIG_CMDLINE | 17 -------------- .../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 22 ------------------- 4 files changed, 2 insertions(+), 39 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CMDLINE create mode 100644 redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CMDLINE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS diff --git a/redhat/configs/common/generic/CONFIG_CMDLINE b/redhat/configs/common/generic/CONFIG_CMDLINE new file mode 100644 index 000000000000..f3083e1e5200 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CMDLINE @@ -0,0 +1 @@ +CONFIG_CMDLINE="" diff --git a/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS new file mode 100644 index 000000000000..f1f7e79da5c3 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS @@ -0,0 +1 @@ +# CONFIG_PPC_QUEUED_SPINLOCKS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CMDLINE b/redhat/configs/pending-common/generic/CONFIG_CMDLINE deleted file mode 100644 index 10611732c5eb..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CMDLINE +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_CMDLINE: -# -# On some platforms, there is currently no way for the boot loader to -# pass arguments to the kernel. For these platforms, you can supply -# some command-line options at build time by entering them here. In -# most cases you will need to specify the root device here. -# -# Symbol: CMDLINE [=] -# Type : string -# Defined at arch/powerpc/Kconfig:882 -# Prompt: Initial kernel command string -# Location: -# -> Kernel options -# -# -# -CONFIG_CMDLINE="" diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS deleted file mode 100644 index 90ecdc77e696..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_PPC_QUEUED_SPINLOCKS: -# -# Say Y here to use queued spinlocks which give better scalability and -# fairness on large SMP and NUMA systems without harming single threaded -# performance. -# -# This option is currently experimental, the code is more complex and -# less tested so it defaults to "N" for the moment. -# -# If unsure, say "N". -# -# Symbol: PPC_QUEUED_SPINLOCKS [=n] -# Type : bool -# Defined at arch/powerpc/Kconfig:497 -# Prompt: Queued spinlocks -# Depends on: SMP [=y] -# Location: -# -> Kernel options -# -# -# -# CONFIG_PPC_QUEUED_SPINLOCKS is not set -- GitLab

4 7

✅ PASS: Test report for kernel 5.10.19-200.fc33 (fedora-33)
by CKI Project 27 Feb '21

27 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.19-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=62729118 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?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 🚧 ✅ 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 🚧 ⚡⚡⚡ stress: stress-ng 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 ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity 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 ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity s390x: 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 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ stress: stress-ng 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 ✅ 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 ⏱.

1 0

A linux-5.11.1.tar.xz that actually contains 5.11 instead of 5.11.1?
by Thorsten Leemhuis 26 Feb '21

26 Feb '21

Lo! The new stable workflow based on kernel-ark confuses me and I want to ask for advice if I got something wrong or if things are really as they appear to me: The sources file in dist.git for the Fedora 34 kernel currently(¹) refers to a file that is called linux-5.11.1.tar.xz – but if you download ("fedpkg sources") and unpack that file and look closer, you'll notice that it actually contains the sources from Linux 5.11 (and not 5.11.1). Is that intentional or just an mistake that someone did somewhere? Because I find that really confusing. Once I looked closer I noticed that the diff from Linux 5.11 -> 5.11.1 can actually be found in the file patch-5.11.1-redhat.patch ( https://src.fedoraproject.org/rpms/kernel/blob/f34/f/patch-5.11.1-redhat.pa… ) - entangled with Fedora specific patches. I didn't try, but I'm therefore pretty sure that rebuilding the kernel SRPM using "--with-vanilla" (for details see https://src.fedoraproject.org/rpms/kernel/blob/f34/f/kernel.spec ) will lead to unexpected results (I guess you will get a kernel that partly thinks it's 5.11.1, but in truth is 5.11; if that acutally boot I suspect users won't be able to spot this). Are things really as described above or did I get something wrong? Because it looks utterly confusing to me. I have some issues with the whole kernel-ark workflow for a while now and hence for a few week already considered asking on the Fedora packaging list (the Fedora Packaging Committe's list) for advice if kernel.spec violates the packaging guidelines too much (a complex package like the kernel likely will always have some issues). I guess this will finally make me do that, but before going down that route I wanted to check here if I got something wrong. CU, knurd (¹) as of https://src.fedoraproject.org/rpms/kernel/c/07992209452cd7ba529ffdbdd83d01d…

2 3

← Newer
1
...
5
6
7
8
9
10
11
...
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2021