kernel June 2021

kernel@lists.fedoraproject.org

6 participants
68 discussions

[OS-BUILD PATCH] [redhat] New configs in fs/cifs
by GitLab Bridge on behalf of redhat-patchlab 07 Jun '21

07 Jun '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_CIFS_SWN_UPCALL: The Service Witness Protocol (SWN) is used to get notifications from a highly available server of resource state changes. This feature enables an upcall mechanism for CIFS which contacts a userspace daemon to establish the DCE/RPC connection to retrieve the cluster available interfaces and resource change notifications. If unsure, say Y. Symbol: CIFS_SWN_UPCALL [=n] Type : bool Defined at fs/cifs/Kconfig:193 Prompt: SWN feature support Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m] Location: -> File systems -> Network File Systems (NETWORK_FILESYSTEMS [=y]) -> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m]) --- Cc: kernel-patches(a)redhat.com Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_CIFS_SWN_UPCALL | 1 + .../generic/CONFIG_CIFS_SWN_UPCALL | 22 ------------------- 2 files changed, 1 insertion(+), 22 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL diff --git a/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL b/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL new file mode 100644 index 000000000000..895af9460510 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL @@ -0,0 +1 @@ +# CONFIG_CIFS_SWN_UPCALL is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL b/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL deleted file mode 100644 index 4b677e712849..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_CIFS_SWN_UPCALL: -# -# The Service Witness Protocol (SWN) is used to get notifications -# from a highly available server of resource state changes. This -# feature enables an upcall mechanism for CIFS which contacts a -# userspace daemon to establish the DCE/RPC connection to retrieve -# the cluster available interfaces and resource change notifications. -# If unsure, say Y. -# -# Symbol: CIFS_SWN_UPCALL [=n] -# Type : bool -# Defined at fs/cifs/Kconfig:193 -# Prompt: SWN feature support -# Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m] -# Location: -# -> File systems -# -> Network File Systems (NETWORK_FILESYSTEMS [=y]) -# -> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m]) -# -# -# -# CONFIG_CIFS_SWN_UPCALL is not set -- GitLab

5 4

✅ PASS: Test report for kernel 5.12.9-200.fc33 (fedora-33)
by CKI Project 06 Jun '21

06 Jun '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.12.9-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=69236556 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: ⏱ Boot 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 Host 2: ⏱ Boot 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 ⏱ stress: stress-ng ppc64le: Host 1: ⏱ Boot 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 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 ⚡⚡⚡ CIFS Connectathon ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ⚡⚡⚡ Ethernet drivers sanity 🚧 ⚡⚡⚡ xarray-idr-radixtree-test Host 3: ✅ Boot 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 s390x: Host 1: ⏱ Boot 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 Host 2: ⏱ Boot test ⏱ xfstests - ext4 ⏱ xfstests - xfs ⏱ Storage: swraid mdadm raid_module test ⏱ xfstests - btrfs ⏱ Storage blktests ⏱ Storage nvme - tcp ⏱ stress: stress-ng x86_64: Host 1: ⏱ Boot 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 ⏱ stress: stress-ng Host 2: ⏱ Boot 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 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 PATCHv2] RHEL: disable io_uring support
by Jeff Moyer (via Email Bridge) 04 Jun '21

04 Jun '21

From: Jeff Moyer <jmoyer(a)redhat.com> RHEL: disable io_uring support Bugzilla: 1964537 Upstream Status: RHEL only io_uring is still under very active development. Disable support for now. We will reassess this decision each minor release. Note: this is a temporary patch which can be reverted after RHEL 9 branches from ark. Signed-off-by: Jeff Moyer <jmoyer(a)redhat.com> diff --git a/init/Kconfig b/init/Kconfig index blahblah..blahblah 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1621,7 +1621,7 @@ config AIO this option saves about 7k. config IO_URING - bool "Enable IO uring support" if EXPERT + bool "Enable IO uring support" select IO_WQ default y help diff --git a/redhat/configs/ark/generic/CONFIG_IO_URING b/redhat/configs/ark/generic/CONFIG_IO_URING new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/CONFIG_IO_URING @@ -0,0 +1 @@ +# CONFIG_IO_URING is not set diff --git a/redhat/configs/fedora/generic/CONFIG_IO_URING b/redhat/configs/fedora/generic/CONFIG_IO_URING new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/fedora/generic/CONFIG_IO_URING @@ -0,0 +1 @@ +CONFIG_IO_URING=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159

4 4

[OS-BUILD PATCH 0/0] [redhat] New configs in drivers/hwtracing
by CKI Gitlab (via Email Bridge) 03 Jun '21

03 Jun '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1085 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_CORESIGHT_TRBE: This driver provides support for percpu Trace Buffer Extension (TRBE). TRBE always needs to be used along with it's corresponding percpu ETE component. ETE generates trace data which is then captured with TRBE. Unlike traditional sink devices, TRBE is a CPU feature accessible via system registers. But it's explicit dependency with trace unit (ETE) requires it to be plugged in as a coresight sink device. To compile this driver as a module, choose M here: the module will be called coresight-trbe. Symbol: CORESIGHT_TRBE [=n] Type : tristate Defined at drivers/hwtracing/coresight/Kconfig:177 Prompt: Trace Buffer Extension (TRBE) driver Depends on: CORESIGHT [=m] && ARM64 [=y] && CORESIGHT_SOURCE_ETM4X [=m] Location: -> Kernel hacking -> arm64 Debugging -> CoreSight Tracing Support (CORESIGHT [=m]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/arm/aarch64/CONFIG_CORESIGHT_TRBE | 1 + redhat/configs/pending-common/generic/CONFIG_CORESIGHT_TRBE | 24 ---------- 2 files changed, 1 insertions(+), 24 deletions(-)

4 3

[OS-BUILD PATCH 0/0] [redhat] New configs in drivers/hid
by CKI Gitlab (via Email Bridge) 03 Jun '21

03 Jun '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1164 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_HID_SEMITEK: Support for Semitek USB keyboards that are not fully compliant with the HID standard. There are many variants, including: - GK61, GK64, GK68, GK84, GK96, etc. - SK61, SK64, SK68, SK84, SK96, etc. - Dierya DK61/DK66 - Tronsmart TK09R - Woo-dy - X-Bows Nature/Knight Symbol: HID_SEMITEK [=n] Type : tristate Defined at drivers/hid/Kconfig:925 Prompt: Semitek USB keyboards Depends on: INPUT [=y] && HID [=y] Location: -> Device Drivers -> HID support -> HID bus support (HID [=y]) -> Special HID drivers --- Cc: Benjamin Tissoires <benjamin.tissoires(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_HID_SEMITEK | 1 + redhat/configs/pending-common/generic/CONFIG_HID_SEMITEK | 27 ---------------- 2 files changed, 1 insertions(+), 27 deletions(-)

3 2

[OS-BUILD PATCH 0/0] Fix sysctl_unprivileged_bpf_disabled sysctl
by Jiri Olsa (via Email Bridge) 02 Jun '21

02 Jun '21

From: Jiri Olsa on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1162 NOTE: Truncated patchset since committer email 'jolsa(a)kernel.org' does not match the submitter's GitLab public email address 'jolsa(a)redhat.com'. There's recent change [1] that adds new config option and sets unprivileged_bpf_disabled to 2 if the option is enabled (CONFIG_BPF_UNPRIV_DEFAULT_OFF). The current RHEL specific behaviour is to set unprivileged_bpf_disabled to 1 by default and add boot command line argument to enable unpriv bpf. The config option is enabled in previous patch, adding the taint for proc/sysctl unprivileged_bpf_disabled setup. # sysctl kernel.unprivileged_bpf_disabled kernel.unprivileged_bpf_disabled = 2 # cat /proc/sys/kernel/tainted 0 # sysctl kernel.unprivileged_bpf_disabled=0 [ 45.751085] Unprivileged BPF has been enabled, tainting the kernel kernel.unprivileged_bpf_disabled = 0 # sysctl kernel.unprivileged_bpf_disabled=1 kernel.unprivileged_bpf_disabled = 1 # sysctl kernel.unprivileged_bpf_disabled=0 sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted # sysctl kernel.unprivileged_bpf_disabled=2 sysctl: setting key "kernel.unprivileged_bpf_disabled": Operation not permitted # cat /proc/sys/kernel/tainted 2147483648 [1] 08389d888287 ("bpf: Add kconfig knob for disabling unpriv bpf by default") [2] 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter") Fixes: 607f0e89af7e ("bpf: set unprivileged_bpf_disabled to 1 by default, add a boot parameter") Signed-off-by: Jiri Olsa <jolsa(a)redhat.com> Signed-off-by: Jiri Olsa <jolsa(a)redhat.com> --- Documentation/admin-guide/kernel-parameters.txt | 7 ++- kernel/bpf/syscall.c | 3 - kernel/sysctl.c | 5 ++ redhat/configs/common/generic/CONFIG_BPF_UNPRIV_DEFAULT_OFF | 1 + redhat/configs/pending-common/generic/CONFIG_BPF_UNPRIV_DEFAULT_OFF | 20 ---------- redhat/configs/pending-fedora/generic/CONFIG_BPF_UNPRIV_DEFAULT_OFF | 20 ---------- 6 files changed, 10 insertions(+), 46 deletions(-)

4 5

[OS-BUILD PATCH] Enable NITRO_ENCLAVES on RHEL
by Vitaly Kuznetsov (via Email Bridge) 02 Jun '21

02 Jun '21

From: Vitaly Kuznetsov <vkuznets(a)redhat.com> Enable NITRO_ENCLAVES on RHEL Nitro Enclaves driver is enabled in RHEL8 and should remain enabled. Move the config setting from fedora/ to common/. Signed-off-by: Vitaly Kuznetsov <vkuznets(a)redhat.com> diff --git a/redhat/configs/fedora/generic/x86/CONFIG_NITRO_ENCLAVES b/redhat/configs/common/generic/x86/CONFIG_NITRO_ENCLAVES rename from redhat/configs/fedora/generic/x86/CONFIG_NITRO_ENCLAVES rename to redhat/configs/common/generic/x86/CONFIG_NITRO_ENCLAVES index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/x86/CONFIG_NITRO_ENCLAVES +++ b/redhat/configs/common/generic/x86/CONFIG_NITRO_ENCLAVES -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1163

4 3

[OS-BUILD PATCHv2] redhat/configs: Set PVPANIC_MMIO for x86 and PVPANIC_PCI for aarch64
by Eric Auger (via Email Bridge) 01 Jun '21

01 Jun '21

From: Eric Auger <eric.auger(a)redhat.com> redhat/configs: Set PVPANIC_MMIO for x86 and PVPANIC_PCI for aarch64 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1961178 Upstream Status: RHEL only Tested: on x86 with libvirt, on ARM with qemu as pvpanic-pci is not yet integrated in libvirt With the introduction of pvpanic-pci new configs were introduced for the MMIO and PCI flavour. On x86, currently none is set so the ISA device is not available (this is a regression). The MMIO flavour must be used on x86_64. On ARM, the PCI one must be set. Signed-off-by: Eric Auger <eric.auger(a)redhat.com> --- v1 -> v2: - s/y/m for PCI and MMIO configs diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC @@ -0,0 +1 @@ +CONFIG_PVPANIC=y diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_MMIO b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_MMIO new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_MMIO @@ -0,0 +1 @@ +# CONFIG_PVPANIC_MMIO is not set diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_PCI b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_PCI new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/arm/aarch64/CONFIG_PVPANIC_PCI @@ -0,0 +1 @@ +CONFIG_PVPANIC_PCI=m diff --git a/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_MMIO b/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_MMIO new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_MMIO @@ -0,0 +1 @@ +CONFIG_PVPANIC_MMIO=m diff --git a/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_PCI b/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_PCI new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/x86/x86_64/CONFIG_PVPANIC_PCI @@ -0,0 +1 @@ +# CONFIG_PVPANIC_PCI is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1158

4 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel June 2021