[OS-BUILD PATCH] Partial revert: Add master merge check
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
I created an optimization to speed up the automated scripts when there was
nothing to merge in redhat/scripts/ci/ark-update-configs.sh under
2d1d129bbe310da5a8751e8e8ff4dc2209337d22
The thought was, if 'master' wasn't updated or needed merging, how can there be
any new configs to add?
Well it turns out that when merge conflicts arise, the merge of master into
os-build has to be done by hand and pushed manually. This usually skips the
new config generation.
The above optimization then skips the config generation on later cron jobs
because the merge already happened (until the master is actually updated).
There is nothing wrong with re-running the config generation script even if
there is nothing to do. Just undo the optimization.
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/scripts/ci/ark-update-configs.sh | 5 -----
1 file changed, 5 deletions(-)
diff --git a/redhat/scripts/ci/ark-update-configs.sh b/redhat/scripts/ci/ark-update-configs.sh
index e8baacdb929e..cf6d201bcaf7 100755
--- a/redhat/scripts/ci/ark-update-configs.sh
+++ b/redhat/scripts/ci/ark-update-configs.sh
@@ -33,7 +33,6 @@ To resolve this, do the following:
git checkout os-build
BRANCH="$(git branch --show-current)"
-HEAD="$(git describe)"
if ! git merge -m "Merge '$UPSTREAM_REF' into '$BRANCH'" "$UPSTREAM_REF"; then
git merge --abort
printf "Merge conflict; halting!\n"
@@ -48,10 +47,6 @@ if ! git merge -m "Merge '$UPSTREAM_REF' into '$BRANCH'" "$UPSTREAM_REF"; then
fi
exit 1
fi
-NEW_HEAD="$(git describe)"
-
-# Merge is already up to date, nothing to do.
-test "$HEAD" != "$NEW_HEAD" || exit 0
# Generates and commits all the pending configs
make FLAVOR=fedora dist-configs-commit
--
GitLab
3 years, 6 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: ff8e5fe4f4a3 - [redhat] kernel-5.10.0-0.rc0.20201016git578a7155c5a1.43
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 6 months
❌ FAIL: Test report for kernel 5.8.15-201.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.15-201.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=53526536
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
x86_64:
❌ LTP
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 3:
✅ 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
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
x86_64:
Host 1:
⚡ 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
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ ACPI table test
❌ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
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
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
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, 6 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 88f2eb4cfa3f - [redhat] kernel-5.10.0-0.rc0.20201015git3e4fb4346c78.42
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 6 months
✅ PASS: Test report for kernel 5.8.15-200.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.15-200.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=53459388
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
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ 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
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
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/hwmon
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_SENSORS_ADM1266:
If you say yes here you get hardware monitoring support for Analog
Devices ADM1266 Cascadable Super Sequencer.
This driver can also be built as a module. If so, the module will
be called adm1266.
Symbol: SENSORS_ADM1266 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:29
Prompt: Analog Devices ADM1266 Sequencer
Depends on: HWMON [=y] && PMBUS [=m] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
Selects: CRC8 [=m]
---
CONFIG_SENSORS_MP2975:
If you say yes here you get hardware monitoring support for MPS
MP2975 Dual Loop Digital Multi-Phase Controller.
This driver can also be built as a module. If so, the module will
be called mp2975.
Symbol: SENSORS_MP2975 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:214
Prompt: MPS MP2975
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_MR75203:
If you say yes here you get support for Moortec MR75203
PVT controller.
This driver can also be built as a module. If so, the module
will be called mr75203.
Symbol: SENSORS_MR75203 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1115
Prompt: Moortec Semiconductor MR75203 PVT Controller
Depends on: HWMON [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
Selects: REGMAP_MMIO [=n]
---
Cc: Dean Nelson <dnelson(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_SENSORS_ADM1266 | 1 +
.../common/generic/CONFIG_SENSORS_MP2975 | 1 +
.../common/generic/CONFIG_SENSORS_MR75203 | 1 +
.../generic/CONFIG_SENSORS_ADM1266 | 22 -------------------
.../generic/CONFIG_SENSORS_MP2975 | 21 ------------------
.../generic/CONFIG_SENSORS_MR75203 | 21 ------------------
6 files changed, 3 insertions(+), 64 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_ADM1266
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_MP2975
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_MR75203
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_ADM1266
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_MP2975
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_MR75203
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_ADM1266 b/redhat/configs/common/generic/CONFIG_SENSORS_ADM1266
new file mode 100644
index 000000000000..fac63d365677
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_ADM1266
@@ -0,0 +1 @@
+# CONFIG_SENSORS_ADM1266 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_MP2975 b/redhat/configs/common/generic/CONFIG_SENSORS_MP2975
new file mode 100644
index 000000000000..018a1d2ea217
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_MP2975
@@ -0,0 +1 @@
+# CONFIG_SENSORS_MP2975 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_MR75203 b/redhat/configs/common/generic/CONFIG_SENSORS_MR75203
new file mode 100644
index 000000000000..6edfde475b0c
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_MR75203
@@ -0,0 +1 @@
+# CONFIG_SENSORS_MR75203 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_ADM1266 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_ADM1266
deleted file mode 100644
index a2aeae8e90be..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_ADM1266
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_SENSORS_ADM1266:
-#
-# If you say yes here you get hardware monitoring support for Analog
-# Devices ADM1266 Cascadable Super Sequencer.
-#
-# This driver can also be built as a module. If so, the module will
-# be called adm1266.
-#
-# Symbol: SENSORS_ADM1266 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/pmbus/Kconfig:29
-# Prompt: Analog Devices ADM1266 Sequencer
-# Depends on: HWMON [=y] && PMBUS [=m] && GPIOLIB [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# -> PMBus support (PMBUS [=m])
-# Selects: CRC8 [=m]
-#
-#
-#
-# CONFIG_SENSORS_ADM1266 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MP2975 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_MP2975
deleted file mode 100644
index 784131652472..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MP2975
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_MP2975:
-#
-# If you say yes here you get hardware monitoring support for MPS
-# MP2975 Dual Loop Digital Multi-Phase Controller.
-#
-# This driver can also be built as a module. If so, the module will
-# be called mp2975.
-#
-# Symbol: SENSORS_MP2975 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/pmbus/Kconfig:214
-# Prompt: MPS MP2975
-# Depends on: HWMON [=y] && PMBUS [=m]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# -> PMBus support (PMBUS [=m])
-#
-#
-#
-# CONFIG_SENSORS_MP2975 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MR75203 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_MR75203
deleted file mode 100644
index b00c30332895..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MR75203
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_MR75203:
-#
-# If you say yes here you get support for Moortec MR75203
-# PVT controller.
-#
-# This driver can also be built as a module. If so, the module
-# will be called mr75203.
-#
-# Symbol: SENSORS_MR75203 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:1115
-# Prompt: Moortec Semiconductor MR75203 PVT Controller
-# Depends on: HWMON [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# Selects: REGMAP_MMIO [=n]
-#
-#
-#
-# CONFIG_SENSORS_MR75203 is not set
--
GitLab
3 years, 6 months
[OS-BUILD PATCH] configs: enable CONFIG_CRYPTO_CTS=y so cts(cbc(aes))
is
available in FIPS mode
by GitLab Bridge on behalf of NefigTut
From: Vladis Dronov <vdronov(a)redhat.com>
Currently the CTS algo is built as a module. This is a problem if any
ciphers using CTS are marked as FIPS-enabled and the system is booted
in FIPS mode, as dracut does not include cts.ko in the initramfs. This
change is necessary for NFS with sec=krb5{,i,p} to work in FIPS mode.
Otherwise, the following panic would result:
[ 8.462065] alg: skcipher: Failed to load transform for cts(cbc(aes)): -2
[ 8.463705] Kernel panic - not syncing: cts(cbc(aes)): cts(cbc(aes)) alg self test failed in fips mode!
Fix this by embedding the CTS code into a kernel, the same way as Fedora
already does. This was tested by a reproducer in bz1855161 #c24, #c28.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1855161
Signed-off-by: Vladis Dronov <vdronov(a)redhat.com>
---
redhat/configs/ark/generic/CONFIG_CRYPTO_CTS | 1 -
.../generic/s390x/zfcpdump => common/generic}/CONFIG_CRYPTO_CTS | 0
redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS | 1 -
3 files changed, 2 deletions(-)
delete mode 100644 redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
rename redhat/configs/{ark/generic/s390x/zfcpdump => common/generic}/CONFIG_CRYPTO_CTS (100%)
delete mode 100644 redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
diff --git a/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS b/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
deleted file mode 100644
index 2529a2fa5379..000000000000
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CTS=m
diff --git a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS b/redhat/configs/common/generic/CONFIG_CRYPTO_CTS
similarity index 100%
rename from redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
rename to redhat/configs/common/generic/CONFIG_CRYPTO_CTS
diff --git a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS b/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
deleted file mode 100644
index e7ff7297caed..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CTS=y
--
GitLab
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-41.test.fc33 (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: a7dc4ff8d8c0 - [redhat] kernel-5.10.0-0.rc0.20201014gitb5fc7a89e58b.40
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 6 months
[OS-BUILD PATCH] configs: enable CONFIG_CRYPTO_CTS=y so cts(cbc(aes)) is available in FIPS mode
by Vladis Dronov
Currently the CTS algo is built as a module. This is a problem if any
ciphers using CTS are marked as FIPS-enabled and the system is booted
in FIPS mode, as dracut does not include cts.ko in the initramfs. This
change is necessary for NFS with sec=krb5{,i,p} to work in FIPS mode.
Otherwise, the following panic would result:
[ 8.462065] alg: skcipher: Failed to load transform for cts(cbc(aes)): -2
[ 8.463705] Kernel panic - not syncing: cts(cbc(aes)): cts(cbc(aes)) alg self test failed in fips mode!
Fix this by embedding the CTS code into a kernel, the same way as Fedora
already does. This was tested by a reproducer in bz1855161 #c24, #c28.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1855161
Signed-off-by: Vladis Dronov <vdronov(a)redhat.com>
---
redhat/configs/ark/generic/CONFIG_CRYPTO_CTS | 1 -
.../generic/s390x/zfcpdump => common/generic}/CONFIG_CRYPTO_CTS | 0
redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS | 1 -
3 files changed, 2 deletions(-)
delete mode 100644 redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
rename redhat/configs/{ark/generic/s390x/zfcpdump => common/generic}/CONFIG_CRYPTO_CTS (100%)
delete mode 100644 redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
diff --git a/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS b/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
deleted file mode 100644
index 2529a2fa5379..000000000000
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_CTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CTS=m
diff --git a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS b/redhat/configs/common/generic/CONFIG_CRYPTO_CTS
similarity index 100%
rename from redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
rename to redhat/configs/common/generic/CONFIG_CRYPTO_CTS
diff --git a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS b/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
deleted file mode 100644
index e7ff7297caed..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_CTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CTS=y
--
2.26.2
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-40.test.fc33 (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: a624d293922c - [redhat] kernel-5.10.0-0.rc0.20201013gitc4439713e82a.39
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 6 months