❌ FAIL: Test report for kernel 5.10.4-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.4-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=58613224
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
ppc64le:
❌ Boot test
❌ Boot test
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
✅ ACPI table 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
🚧 ✅ 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
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:
✅ 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 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ 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: swraid mdadm raid_module test
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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
❌ FAIL: Test report for kernel 5.10.3-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.3-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=58544686
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
ppc64le:
❌ Boot test
❌ Boot test
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
✅ 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
🚧 ✅ 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
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
✅ 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
⚡⚡⚡ ACPI table 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
🚧 ✅ 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: swraid mdadm raid_module test
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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, 4 months
[NIT] error: %changelog not in descending chronological order
by Paul Bolle
Hi Justin,
Nobody noticed, so this is just a nit, but ever since the v5.8.14 build for
fc32 there's this in the fc32 build logs:
error: %changelog not in descending chronological order
I think what triggers this is that you've recently added extended the
datestamp on your changelog entries with timestamps. Eg:
* Wed Oct 7 07:21:23 CDT 2020 Justin M. Forbes <jforbes(a)fedoraproject.org> - 5.8.14-200
But if the preceding changelog entry doesn't have a timestamp, like:
* Wed Oct 7 2020 Peter Robinson <pbrobinson(a)fedoraproject.org>
rpmbuild spits out an "error:" but merrily continues the build! (I have no
idea how that works. Both the timestamp comparison and the build ignoring an
error.)
Do people care enough to try to fix this?
Thanks,
Paul Bolle
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in arch/x86
by GitLab Bridge on behalf of redhat-patchlab
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_XEN_PVHVM_GUEST:
Support running as a Xen PVHVM guest.
Symbol: XEN_PVHVM_GUEST [=y]
Type : bool
Defined at arch/x86/xen/Kconfig:62
Prompt: Xen PVHVM guest support
Depends on: HYPERVISOR_GUEST [=y] && XEN_PVHVM [=y] && PCI [=y]
Location:
-> Processor type and features
-> Linux guest support (HYPERVISOR_GUEST [=y])
-> Xen guest support (XEN [=y])
---
Cc: David Arcari <darcari(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_XEN_PVHVM_GUEST | 1 +
.../generic/CONFIG_XEN_PVHVM_GUEST | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_XEN_PVHVM_GUEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XEN_PVHVM_GUEST
diff --git a/redhat/configs/common/generic/CONFIG_XEN_PVHVM_GUEST b/redhat/configs/common/generic/CONFIG_XEN_PVHVM_GUEST
new file mode 100644
index 000000000000..d971c335c658
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_XEN_PVHVM_GUEST
@@ -0,0 +1 @@
+CONFIG_XEN_PVHVM_GUEST=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_XEN_PVHVM_GUEST b/redhat/configs/pending-common/generic/CONFIG_XEN_PVHVM_GUEST
deleted file mode 100644
index 02723a18cf42..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_XEN_PVHVM_GUEST
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_XEN_PVHVM_GUEST:
-#
-# Support running as a Xen PVHVM guest.
-#
-# Symbol: XEN_PVHVM_GUEST [=y]
-# Type : bool
-# Defined at arch/x86/xen/Kconfig:62
-# Prompt: Xen PVHVM guest support
-# Depends on: HYPERVISOR_GUEST [=y] && XEN_PVHVM [=y] && PCI [=y]
-# Location:
-# -> Processor type and features
-# -> Linux guest support (HYPERVISOR_GUEST [=y])
-# -> Xen guest support (XEN [=y])
-#
-#
-#
-CONFIG_XEN_PVHVM_GUEST=y
--
GitLab
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in drivers/ptp
by GitLab Bridge on behalf of redhat-patchlab
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_PTP_1588_CLOCK_OCP:
This driver adds support for an OpenCompute time card.
The OpenCompute time card is an atomic clock along with
a GPS receiver that provides a Grandmaster clock source
for a PTP enabled network.
More information is available at http://www.timingcard.com/
Symbol: PTP_1588_CLOCK_OCP [=n]
Type : tristate
Defined at drivers/ptp/Kconfig:154
Prompt: OpenCompute TimeCard as PTP clock
Depends on: PTP_1588_CLOCK [=y] && HAS_IOMEM [=y] && PCI [=y]
Location:
-> Device Drivers
-> PTP clock support
---
Cc: Jiri Benc <jbenc(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PTP_1588_CLOCK_OCP | 1 +
.../generic/CONFIG_PTP_1588_CLOCK_OCP | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PTP_1588_CLOCK_OCP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PTP_1588_CLOCK_OCP
diff --git a/redhat/configs/common/generic/CONFIG_PTP_1588_CLOCK_OCP b/redhat/configs/common/generic/CONFIG_PTP_1588_CLOCK_OCP
new file mode 100644
index 000000000000..466cead8f0a5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PTP_1588_CLOCK_OCP
@@ -0,0 +1 @@
+# CONFIG_PTP_1588_CLOCK_OCP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PTP_1588_CLOCK_OCP b/redhat/configs/pending-common/generic/CONFIG_PTP_1588_CLOCK_OCP
deleted file mode 100644
index af2256528ed8..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PTP_1588_CLOCK_OCP
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_PTP_1588_CLOCK_OCP:
-#
-# This driver adds support for an OpenCompute time card.
-#
-# The OpenCompute time card is an atomic clock along with
-# a GPS receiver that provides a Grandmaster clock source
-# for a PTP enabled network.
-#
-# More information is available at http://www.timingcard.com/
-#
-# Symbol: PTP_1588_CLOCK_OCP [=n]
-# Type : tristate
-# Defined at drivers/ptp/Kconfig:154
-# Prompt: OpenCompute TimeCard as PTP clock
-# Depends on: PTP_1588_CLOCK [=y] && HAS_IOMEM [=y] && PCI [=y]
-# Location:
-# -> Device Drivers
-# -> PTP clock support
-#
-#
-#
-# CONFIG_PTP_1588_CLOCK_OCP is not set
--
GitLab
3 years, 4 months
"No CCs" label & cki-bot
by Prarit Bhargava
It seems that cki-bot doesn't like it when I remove the "No CCs" label from an
MR. You can see this odd behaviour in !741:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/741
I ran a script to identify all the mislabeled "No CCs" MRs, and tried to remove
it by hand from !741. The cki-bot immediately steps in and relabels it.
Is there some step I'm missing? !741 clearly has CCs. The only thing I can
think of is that cki-bot's webhook is broken.
P.
3 years, 4 months
Re: [OS-BUILD PATCHv4 0/3] [redhat] New configs in drivers/i2c
by Mark Salter
I added this comment to MR yesterday:
CONFIG_I2C_MLXBF is correct.
CONFIG_I2C_SLAVE_TESTUNIT looks generic. Not sure why it was moved to aarch64-specific.
Mark
On Wed, 2020-12-23 at 02:24 -0500, Gopal Tiwari wrote:
> Waiting for msalter's confirmation. Though looks fine to me unless Mark has any objections.
>
> Thanks David.
>
> Gopal..
>
> ----- Original Message -----
> From: "David Arcari" <darcari(a)redhat.com>
> To: kernel(a)lists.fedoraproject.org
> Cc: gtiwari(a)redhat.com, kernel-team(a)fedoraproject.org, ptalbert(a)redhat.com, "Mark Salter" <msalter(a)redhat.com>
> Sent: Tuesday, December 22, 2020 10:02:19 PM
> Subject: Re: [OS-BUILD PATCHv4 0/3] [redhat] New configs in drivers/i2c
>
>
> +msalter
>
> I think this is correct now, Mark?
>
> Thanks,
>
> -DA
>
> On 12/22/20 11:19 AM, GitLab Bridge on behalf of jeremycline wrote:
> > From: jeremycline on gitlab.com
> >
> > 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_I2C_MLXBF:
> >
> > Enabling this option will add I2C SMBus support for Mellanox BlueField
> > system.
> >
> > This driver can also be built as a module. If so, the module will be
> > called i2c-mlxbf.
> >
> > This driver implements an I2C SMBus host controller and enables both
> > master and slave functions.
> >
> > Symbol: I2C_MLXBF [=n]
> > Type : tristate
> > Defined at drivers/i2c/busses/Kconfig:734
> > Prompt: Mellanox BlueField I2C controller
> > Depends on: I2C [=y] && HAS_IOMEM [=y] && ARM64 [=y]
> > Location:
> > -> Device Drivers
> > -> I2C support
> > -> I2C support (I2C [=y])
> > -> I2C Hardware Bus support
> >
> > ---
> >
> > CONFIG_I2C_SLAVE_TESTUNIT:
> >
> > This backend can be used to trigger test cases for I2C bus masters
> > which require a remote device with certain capabilities, e.g.
> > multi-master, SMBus Host Notify, etc. Please read
> > Documentation/i2c/slave-testunit-backend.rst for further details.
> >
> > Symbol: I2C_SLAVE_TESTUNIT [=n]
> > Type : tristate
> > Defined at drivers/i2c/Kconfig:128
> > Prompt: I2C eeprom testunit driver
> > Depends on: I2C [=y] && I2C_SLAVE [=y]
> > Location:
> > -> Device Drivers
> > -> I2C support
> > -> I2C support (I2C [=y])
> > -> I2C slave support (I2C_SLAVE [=y])
> >
> > ---
> >
> > Cc: Gopal Tiwari <gtiwari(a)redhat.com>
> > Cc: David Arcari <darcari(a)redhat.com>
> > Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
> >
>
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in arch/Kconfig
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_STATIC_CALL_SELFTEST:
Boot time self-test of the call patching code.
Symbol: STATIC_CALL_SELFTEST [=n]
Type : bool
Defined at arch/Kconfig:109
Prompt: Static call selftest
Depends on: HAVE_STATIC_CALL [=y]
Location:
-> General architecture-dependent options
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_STATIC_CALL_SELFTEST | 1 +
.../generic/CONFIG_STATIC_CALL_SELFTEST | 15 ---------------
2 files changed, 1 insertion(+), 15 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_STATIC_CALL_SELFTEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_STATIC_CALL_SELFTEST
diff --git a/redhat/configs/common/generic/CONFIG_STATIC_CALL_SELFTEST b/redhat/configs/common/generic/CONFIG_STATIC_CALL_SELFTEST
new file mode 100644
index 000000000000..ac1a3526ff7a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_STATIC_CALL_SELFTEST
@@ -0,0 +1 @@
+# CONFIG_STATIC_CALL_SELFTEST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_STATIC_CALL_SELFTEST b/redhat/configs/pending-common/generic/CONFIG_STATIC_CALL_SELFTEST
deleted file mode 100644
index 392dde5a531d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_STATIC_CALL_SELFTEST
+++ /dev/null
@@ -1,15 +0,0 @@
-# CONFIG_STATIC_CALL_SELFTEST:
-#
-# Boot time self-test of the call patching code.
-#
-# Symbol: STATIC_CALL_SELFTEST [=n]
-# Type : bool
-# Defined at arch/Kconfig:109
-# Prompt: Static call selftest
-# Depends on: HAVE_STATIC_CALL [=y]
-# Location:
-# -> General architecture-dependent options
-#
-#
-#
-# CONFIG_STATIC_CALL_SELFTEST is not set
--
GitLab
3 years, 4 months
[OS-BUILD PATCH] [redhat] New configs in drivers/crypto
by GitLab Bridge on behalf of redhat-patchlab
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_CRYPTO_DEV_HISI_TRNG:
Support for HiSilicon TRNG Driver.
Symbol: CRYPTO_DEV_HISI_TRNG [=n]
Type : tristate
Defined at drivers/crypto/hisilicon/Kconfig:75
Prompt: Support for HISI TRNG Driver
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && ARM64 [=y] && ACPI [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: HW_RANDOM [=y] && CRYPTO_RNG [=y]
---
CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4:
Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) AES and
SM4 cihper hardware acceleration for use with Crypto API.
Provides HW acceleration for the following transformations:
cbc(aes), ctr(aes), ccm(aes), gcm(aes), cbc(sm4), ctr(sm4), ccm(sm4)
and gcm(sm4).
Optionally, support for the following transformations can also be
enabled: ecb(aes), cts(cbc(aes)), ecb(sm4) and cts(cbc(sm4)).
Symbol: CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 [=n]
Type : tristate
Defined at drivers/crypto/keembay/Kconfig:1
Prompt: Support for Intel Keem Bay OCS AES/SM4 HW acceleration
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && (OF [=y] || COMPILE_TEST [=n])
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_AEAD [=y] && CRYPTO_ENGINE [=n]
---
CONFIG_CRYPTO_DEV_QAT_4XXX:
Support for Intel(R) QuickAssist Technology QAT_4xxx
for accelerating crypto and compression workloads.
To compile this as a module, choose M here: the module
will be called qat_4xxx.
Symbol: CRYPTO_DEV_QAT_4XXX [=n]
Type : tristate
Defined at drivers/crypto/qat/Kconfig:49
Prompt: Support for Intel(R) QAT_4XXX
Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && X86 [=y] && PCI [=y]
Location:
-> Cryptographic API (CRYPTO [=y])
-> Hardware crypto devices (CRYPTO_HW [=y])
Selects: CRYPTO_DEV_QAT [=m]
---
Cc: Herbert Xu <herbert.xu(a)redhat.com>
Cc: "David S. Miller" <davem(a)redhat.com>
Cc: Ondrej Mosnacek <omosnace(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_CRYPTO_DEV_HISI_TRNG | 1 +
.../CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 | 1 +
.../common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX | 1 +
.../generic/CONFIG_CRYPTO_DEV_HISI_TRNG | 17 -------------
.../CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 | 25 -------------------
.../generic/CONFIG_CRYPTO_DEV_QAT_4XXX | 21 ----------------
6 files changed, 3 insertions(+), 63 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
new file mode 100644
index 000000000000..44184cc72db2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
@@ -0,0 +1 @@
+# CONFIG_CRYPTO_DEV_HISI_TRNG is not set
diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
new file mode 100644
index 000000000000..415503dd9113
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
@@ -0,0 +1 @@
+# CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 is not set
diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
new file mode 100644
index 000000000000..54fd0faec1c8
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
@@ -0,0 +1 @@
+# CONFIG_CRYPTO_DEV_QAT_4XXX is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
deleted file mode 100644
index 273befa0d40a..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_HISI_TRNG
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_CRYPTO_DEV_HISI_TRNG:
-#
-# Support for HiSilicon TRNG Driver.
-#
-# Symbol: CRYPTO_DEV_HISI_TRNG [=n]
-# Type : tristate
-# Defined at drivers/crypto/hisilicon/Kconfig:75
-# Prompt: Support for HISI TRNG Driver
-# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && ARM64 [=y] && ACPI [=y]
-# Location:
-# -> Cryptographic API (CRYPTO [=y])
-# -> Hardware crypto devices (CRYPTO_HW [=y])
-# Selects: HW_RANDOM [=y] && CRYPTO_RNG [=y]
-#
-#
-#
-# CONFIG_CRYPTO_DEV_HISI_TRNG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
deleted file mode 100644
index 2a2234550e3d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4:
-#
-# Support for Intel Keem Bay Offload and Crypto Subsystem (OCS) AES and
-# SM4 cihper hardware acceleration for use with Crypto API.
-#
-# Provides HW acceleration for the following transformations:
-# cbc(aes), ctr(aes), ccm(aes), gcm(aes), cbc(sm4), ctr(sm4), ccm(sm4)
-# and gcm(sm4).
-#
-# Optionally, support for the following transformations can also be
-# enabled: ecb(aes), cts(cbc(aes)), ecb(sm4) and cts(cbc(sm4)).
-#
-# Symbol: CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 [=n]
-# Type : tristate
-# Defined at drivers/crypto/keembay/Kconfig:1
-# Prompt: Support for Intel Keem Bay OCS AES/SM4 HW acceleration
-# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && (OF [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Cryptographic API (CRYPTO [=y])
-# -> Hardware crypto devices (CRYPTO_HW [=y])
-# Selects: CRYPTO_SKCIPHER [=y] && CRYPTO_AEAD [=y] && CRYPTO_ENGINE [=n]
-#
-#
-#
-# CONFIG_CRYPTO_DEV_KEEMBAY_OCS_AES_SM4 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
deleted file mode 100644
index 5b3262998540..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_DEV_QAT_4XXX
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_CRYPTO_DEV_QAT_4XXX:
-#
-# Support for Intel(R) QuickAssist Technology QAT_4xxx
-# for accelerating crypto and compression workloads.
-#
-# To compile this as a module, choose M here: the module
-# will be called qat_4xxx.
-#
-# Symbol: CRYPTO_DEV_QAT_4XXX [=n]
-# Type : tristate
-# Defined at drivers/crypto/qat/Kconfig:49
-# Prompt: Support for Intel(R) QAT_4XXX
-# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && X86 [=y] && PCI [=y]
-# Location:
-# -> Cryptographic API (CRYPTO [=y])
-# -> Hardware crypto devices (CRYPTO_HW [=y])
-# Selects: CRYPTO_DEV_QAT [=m]
-#
-#
-#
-# CONFIG_CRYPTO_DEV_QAT_4XXX is not set
--
GitLab
3 years, 4 months
[OS-BUILD PATCH 0/20] [redhat] All shell scripts: Fix syntax flagged
by
shellcheck
by GitLab Bridge on behalf of bcrocker
From: bcrocker on gitlab.com
Fix syntax flagged by shellcheck in all scripts in the redhat/ subtree.
A complete 'git log -p' of all commits on this branch can be found at:
http://pastebin.test.redhat.com/917268
SC2001: See if you can use ${variable//search/replace} instead.\
SC2002: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..'
instead.\
SC2006: Use $(...) notation instead of legacy backticked `...`.\
SC2007: Use $((..)) instead of deprecated $[..]\
SC2013: To read lines rather than words, pipe/redirect to a 'while read'
loop. ???\
SC2034: <variable> appears unused. Verify use (or export if used
externally).\
SC2035: Use ./*glob* or -- *glob* so names with dashes won't become
options.\
SC2038: Use -print0/-0 or find -exec + to allow for non-alphanumeric
filenames.\
SC2045: Iterating over ls output is fragile. Use globs.\
SC2046: Quote this (command) to prevent word splitting.\
SC2068: Double quote array expansions to avoid re-splitting elements.\
SC2086: Double quote to prevent globbing and word splitting.\
SC2144: -f doesn't work with globs. Use a for loop.\
SC2145: Argument mixes string and array. Use * or separate argument.\
SC2155: Declare and assign separately to avoid masking return values. \
SC2162: read without -r will mangle backslashes.\
SC2166: Prefer [ p ] && [ q ] as [ p -a q ] is not well defined.\
SC2181: Check exit code directly with e.g. 'if mycmd;', not indirectly
with $?.\
SC2196: egrep is non-standard and deprecated. Use grep -E instead.\
SC2231: Quote expansions in this for-loop glob to prevent
wordsplitting.\
SC2236: Use -z instead of ! -n.\
Change to #!/bin/bash explicitly to allow\
SC2039: bash-isms
Disable:\
SC2164: Use 'pushd ... || exit' or 'pushd ... || return' in case pushd
fails.\
SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails.
Disable checking for one instance of:
SC2059: Don't use variables in the printf format string. Use printf
"..%s.." "$foo".
The pattern in question is a multi-line string; the shellcheck wiki,\
https://github.com/koalaman/shellcheck/wiki/SC2059, acknowledges that\
there is no good rewrite for this construct and recommends disabling\
the warning.
3 years, 4 months
