[OS-BUILD PATCH] [redhat] New configs in drivers/watchdog
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_ARM_SMC_WATCHDOG:
Say Y here to include support for a watchdog timer
implemented by the EL3 Secure Monitor on ARM platforms.
Requires firmware support.
To compile this driver as a module, choose M here: the
module will be called arm_smc_wdt.
Symbol: ARM_SMC_WATCHDOG [=n]
Type : tristate
Defined at drivers/watchdog/Kconfig:871
Prompt: ARM Secure Monitor Call based watchdog support
Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
Location:
-> Device Drivers
-> Watchdog Timer Support (WATCHDOG [=y])
Selects: WATCHDOG_CORE [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_ARM_SMC_WATCHDOG | 1 +
.../generic/CONFIG_ARM_SMC_WATCHDOG | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
diff --git a/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
new file mode 100644
index 000000000000..5292578ce994
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
@@ -0,0 +1 @@
+# CONFIG_ARM_SMC_WATCHDOG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
deleted file mode 100644
index af24ce5fab9c..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_ARM_SMC_WATCHDOG:
-#
-# Say Y here to include support for a watchdog timer
-# implemented by the EL3 Secure Monitor on ARM platforms.
-# Requires firmware support.
-# To compile this driver as a module, choose M here: the
-# module will be called arm_smc_wdt.
-#
-# Symbol: ARM_SMC_WATCHDOG [=n]
-# Type : tristate
-# Defined at drivers/watchdog/Kconfig:871
-# Prompt: ARM Secure Monitor Call based watchdog support
-# Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
-# Location:
-# -> Device Drivers
-# -> Watchdog Timer Support (WATCHDOG [=y])
-# Selects: WATCHDOG_CORE [=y]
-#
-#
-#
-# CONFIG_ARM_SMC_WATCHDOG is not set
--
2.26.2
3 years
[OS-BUILD PATCHv2 0/0] [redhat] New configs in drivers/clk
by CKI Gitlab (via Email Bridge)
From: CKI Gitlab on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/832
NOTE: Truncated patchset due to missing @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.
---
---
---
---
Cc: Mark Salter <msalter(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
3 years
[OS-BUILD PATCH] [redhat] New configs in drivers/dma-buf
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/dma-buf
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_DMABUF_DEBUG:
This option enables additional checks for DMA-BUF importers and
exporters. Specifically it validates that importers do not peek at the
underlying struct page when they import a buffer.
Symbol: DMABUF_DEBUG [=n]
Type : bool
Defined at drivers/dma-buf/Kconfig:53
Prompt: DMA-BUF debug checks
Location:
-> Device Drivers
-> DMABUF options
---
Cc: Lyude Paul <lyude(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG b/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG
@@ -0,0 +1 @@
+# CONFIG_DMABUF_DEBUG is not set
diff a/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG b/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG
--- a/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_DMABUF_DEBUG:
-#
-# This option enables additional checks for DMA-BUF importers and
-# exporters. Specifically it validates that importers do not peek at the
-# underlying struct page when they import a buffer.
-#
-# Symbol: DMABUF_DEBUG [=n]
-# Type : bool
-# Defined at drivers/dma-buf/Kconfig:53
-# Prompt: DMA-BUF debug checks
-# Location:
-# -> Device Drivers
-# -> DMABUF options
-#
-#
-#
-# CONFIG_DMABUF_DEBUG is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/903
3 years
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
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_CSD_LOCK_WAIT_DEBUG:
This option enables debug prints when CPUs are slow to respond
to the smp_call_function*() IPI wrappers. These debug prints
include the IPI handler function currently executing (if any)
and relevant stack traces.
Symbol: CSD_LOCK_WAIT_DEBUG [=n]
Type : bool
Defined at lib/Kconfig.debug:1380
Prompt: Debugging for csd_lock_wait(), called from smp_call_function*()
Depends on: DEBUG_KERNEL [=y] && 64BIT [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
---
CONFIG_SCF_TORTURE_TEST:
This option provides a kernel module that runs torture tests
on the smp_call_function() family of primitives. The kernel
module may be built after the fact on the running kernel to
be tested, if desired.
Symbol: SCF_TORTURE_TEST [=n]
Type : tristate
Defined at lib/Kconfig.debug:1370
Prompt: torture tests for smp_call_function*()
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> Lock Debugging (spinlocks, mutexes, etc...)
Selects: TORTURE_TEST [=n]
---
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG | 1 +
.../common/generic/CONFIG_SCF_TORTURE_TEST | 1 +
.../generic/CONFIG_CSD_LOCK_WAIT_DEBUG | 19 ------------------
.../generic/CONFIG_SCF_TORTURE_TEST | 20 -------------------
4 files changed, 2 insertions(+), 39 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
create mode 100644 redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST
diff --git a/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG b/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
new file mode 100644
index 000000000000..086e41bbfcf8
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
@@ -0,0 +1 @@
+# CONFIG_CSD_LOCK_WAIT_DEBUG is not set
diff --git a/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST b/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST
new file mode 100644
index 000000000000..53ebe3b18974
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST
@@ -0,0 +1 @@
+# CONFIG_SCF_TORTURE_TEST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG b/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
deleted file mode 100644
index d2e1af1bda65..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_CSD_LOCK_WAIT_DEBUG:
-#
-# This option enables debug prints when CPUs are slow to respond
-# to the smp_call_function*() IPI wrappers. These debug prints
-# include the IPI handler function currently executing (if any)
-# and relevant stack traces.
-#
-# Symbol: CSD_LOCK_WAIT_DEBUG [=n]
-# Type : bool
-# Defined at lib/Kconfig.debug:1380
-# Prompt: Debugging for csd_lock_wait(), called from smp_call_function*()
-# Depends on: DEBUG_KERNEL [=y] && 64BIT [=y]
-# Location:
-# -> Kernel hacking
-# -> Lock Debugging (spinlocks, mutexes, etc...)
-#
-#
-#
-# CONFIG_CSD_LOCK_WAIT_DEBUG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST b/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST
deleted file mode 100644
index d22be82b0415..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_SCF_TORTURE_TEST:
-#
-# This option provides a kernel module that runs torture tests
-# on the smp_call_function() family of primitives. The kernel
-# module may be built after the fact on the running kernel to
-# be tested, if desired.
-#
-# Symbol: SCF_TORTURE_TEST [=n]
-# Type : tristate
-# Defined at lib/Kconfig.debug:1370
-# Prompt: torture tests for smp_call_function*()
-# Depends on: DEBUG_KERNEL [=y]
-# Location:
-# -> Kernel hacking
-# -> Lock Debugging (spinlocks, mutexes, etc...)
-# Selects: TORTURE_TEST [=n]
-#
-#
-#
-# CONFIG_SCF_TORTURE_TEST is not set
--
GitLab
3 years
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.kgdb
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_KGDB_HONOUR_BLOCKLIST:
If set to Y the debug core will use the kprobe blocklist to
identify symbols where it is unsafe to set breakpoints.
In particular this disallows instrumentation of functions
called during debug trap handling and thus makes it very
difficult to inadvertently provoke recursive trap handling.
If unsure, say Y.
Symbol: KGDB_HONOUR_BLOCKLIST [=y]
Type : bool
Defined at lib/Kconfig.kgdb:27
Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
-> KGDB: kernel debugger (KGDB [=y])
Selects: KPROBES [=y]
---
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 1 +
.../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
diff --git a/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
new file mode 100644
index 000000000000..7da79f661883
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
@@ -0,0 +1 @@
+CONFIG_KGDB_HONOUR_BLOCKLIST=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
deleted file mode 100644
index 224aca014283..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_KGDB_HONOUR_BLOCKLIST:
-#
-# If set to Y the debug core will use the kprobe blocklist to
-# identify symbols where it is unsafe to set breakpoints.
-# In particular this disallows instrumentation of functions
-# called during debug trap handling and thus makes it very
-# difficult to inadvertently provoke recursive trap handling.
-#
-# If unsure, say Y.
-#
-# Symbol: KGDB_HONOUR_BLOCKLIST [=y]
-# Type : bool
-# Defined at lib/Kconfig.kgdb:27
-# Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
-# Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
-# Location:
-# -> Kernel hacking
-# -> Generic Kernel Debugging Instruments
-# -> KGDB: kernel debugger (KGDB [=y])
-# Selects: KPROBES [=y]
-#
-#
-#
-CONFIG_KGDB_HONOUR_BLOCKLIST=y
--
GitLab
3 years, 1 month
✅ PASS: Test report for kernel 5.11.10-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.10-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=64586288
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
✅ ACPI table test
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
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
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
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
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
⚡⚡⚡ LTP
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ 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
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ 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
⚡⚡⚡ LTP
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
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
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ 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
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, 1 month
[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
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_PPC_PROT_SAO_LPAR:
This option adds support for PROT_SAO mappings from userspace
inside LPARs on supported CPUs.
This may cause issues when performing guest migration from
a CPU that supports SAO to one that does not.
If unsure, say N here.
Symbol: PPC_PROT_SAO_LPAR [=n]
Type : bool
Defined at arch/powerpc/Kconfig:863
Prompt: Support PROT_SAO mappings in LPARs
Depends on: PPC_BOOK3S_64 [=y]
Location:
-> Kernel options
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PPC_PROT_SAO_LPAR | 1 +
.../generic/CONFIG_PPC_PROT_SAO_LPAR | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
diff --git a/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
new file mode 100644
index 000000000000..bea5ce6ad2b5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
@@ -0,0 +1 @@
+# CONFIG_PPC_PROT_SAO_LPAR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
deleted file mode 100644
index 88471b97ec8d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_PPC_PROT_SAO_LPAR:
-#
-# This option adds support for PROT_SAO mappings from userspace
-# inside LPARs on supported CPUs.
-#
-# This may cause issues when performing guest migration from
-# a CPU that supports SAO to one that does not.
-#
-# If unsure, say N here.
-#
-# Symbol: PPC_PROT_SAO_LPAR [=n]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:863
-# Prompt: Support PROT_SAO mappings in LPARs
-# Depends on: PPC_BOOK3S_64 [=y]
-# Location:
-# -> Kernel options
-#
-#
-#
-# CONFIG_PPC_PROT_SAO_LPAR is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
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_PPC_RTAS_FILTER:
The RTAS syscall API has security issues that could be used to
compromise system integrity. This option enforces restrictions on the
RTAS calls and arguments passed by userspace programs to mitigate
these issues.
Say Y unless you know what you are doing and the filter is causing
problems for you.
Symbol: PPC_RTAS_FILTER [=y]
Type : bool
Defined at arch/powerpc/Kconfig:991
Prompt: Enable filtering of RTAS syscalls
Depends on: PPC_RTAS [=y]
Location:
-> Kernel options
---
Cc: kernel-patches(a)redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PPC_RTAS_FILTER | 1 +
.../generic/CONFIG_PPC_RTAS_FILTER | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
diff --git a/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
new file mode 100644
index 000000000000..7470f4d4f0fe
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
@@ -0,0 +1 @@
+CONFIG_PPC_RTAS_FILTER=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
deleted file mode 100644
index 6105fa8baae5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_PPC_RTAS_FILTER:
-#
-# The RTAS syscall API has security issues that could be used to
-# compromise system integrity. This option enforces restrictions on the
-# RTAS calls and arguments passed by userspace programs to mitigate
-# these issues.
-#
-# Say Y unless you know what you are doing and the filter is causing
-# problems for you.
-#
-# Symbol: PPC_RTAS_FILTER [=y]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:991
-# Prompt: Enable filtering of RTAS syscalls
-# Depends on: PPC_RTAS [=y]
-# Location:
-# -> Kernel options
-#
-#
-#
-CONFIG_PPC_RTAS_FILTER=y
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] Add git config hook
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
The kernel workflow is adding complexity. Let's hide some of that complexity
behind git aliases. Instead of having the developer manually add them all
the time, add a make command to 'include' kernel aliases.
A new command 'make rh-gitsetup' runs
git config --local --add include.path "../redhat/kernel.gitconfig"
and adds an include to the local repo's .git/config file.
Over time more workflow commands can be added to help developers.
Start with a stub config file.
V5: text cleanups
V4: s/gitconfig/gitsetup
V3: expand comment in kernel.gitconfig
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/Makefile | 6 ++++++
redhat/kernel.gitconfig | 10 ++++++++++
2 files changed, 16 insertions(+)
create mode 100644 redhat/kernel.gitconfig
diff --git a/redhat/Makefile b/redhat/Makefile
index 0118e5b9e2e9..9236fdb1418a 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -133,6 +133,10 @@ rh-kabi-dw-check: rh-kabi
@echo "**** End of KABI DWARF-based comparison report ****"
@rm -rf $(KABIDW)/base/$(CURARCH).tmp
+rh-gitsetup:
+ @git config --get include.path | grep -q 'redhat/kernel.gitconfig' || \
+ git config --local --add include.path "../redhat/kernel.gitconfig"
+
rh-configs-commit: rh-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh $(FLAVOR) 1; \
./process_configs.sh -z $(PACKAGE_NAME) $(KVERSION) "" $(FLAVOR)
@@ -363,6 +367,7 @@ rh-help:
@echo ' rh-cross-all-rpms - Build RPMs for all supported archs using a cross compiler.'
@echo ''
@echo 'Configuration targets:'
+ @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config'
@echo ' rh-configs - Create RHEL config files in redhat/config/.'
@echo ''
@echo 'For detailed description and full list of targets, run `make rh-full-help`.'
@@ -442,6 +447,7 @@ rh-full-help:
@echo ''
@echo 'Configuration targets:'
+ @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config'
@echo ' rh-configs - Creates config files for RHEL $(RHEL_MAJOR) architectures, cleans them'
@echo ' by running make nonint_oldconfig, and copies them to'
@echo ' redhat/configs/ directory. This is the target to use for a config!'
diff --git a/redhat/kernel.gitconfig b/redhat/kernel.gitconfig
new file mode 100644
index 000000000000..6fd63c7ac1aa
--- /dev/null
+++ b/redhat/kernel.gitconfig
@@ -0,0 +1,10 @@
+# The kernel workflow is growing in complexity. Developers can not always
+# remember all the nuisances involved.
+# This file is meant to aid developers by providing wrappers around some
+# parts of the workflow that everyone can use.
+#
+# Examples include 'aliases' for git-push options or a shortcut for
+# executing workflow checks before pushing.
+#
+# Please do not include personal information here.
+[alias]
--
2.26.2
3 years, 1 month
✅ PASS: Test report for kernel 5.11.9-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.9-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=64501742
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
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ 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
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
ppc64le:
Host 1:
✅ Boot test
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
Host 2:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: lvm device-mapper test
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: swraid mdadm raid_module test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ stress: stress-ng
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
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
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ stress: stress-ng
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
⚡⚡⚡ LTP
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
x86_64:
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
Host 2:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ 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
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, 1 month