✅ PASS: Test report for kernel 5.12.5-200.fc33 (fedora-33)

2021-05-19 Thread CKI Project
Hello,

We ran automated tests on the following kernel build:

Kernel package: kernel-5.12.5-200.fc33
 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=68274900

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?prefix=datawarehouse-public/2021/05/19/306127378

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
   ⏱  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

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

  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:
   ⏱  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
   ✅ Storage: swraid mdadm raid_module test
    ✅ Storage blktests
   ⏱  Storage nvme - tcp
   ⏱  stress: stress-ng

Host 2:
   ✅ 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

  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 ⏱.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCH 0/3] ark: Set Architecture Level Set to Z14 for s390

2021-05-19 Thread Justin Forbes (via Email Bridge)
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_579901839

As this is the merge request creating the dependency on those, the best
path forward is to put them in common instead of pending-common. The
make dist-configs breakage doesn't happen until this MR goes in, and if
they are in common it won't happen after it goes in either.  If they
need reviewers from other areas, you can CC them and they will get
reviewed that way, or we can try to add the right people
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCH 0/3] ark: Set Architecture Level Set to Z14 for s390

2021-05-19 Thread Philipp Rudo (via Email Bridge)
From: Philipp Rudo on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_579786679

ok, I naively thought that pending-common was the staging area and
everything contained in it will be included in the next round of config
review.
What's the correct way to proceed? Not having them set isn't an option
for me as that would break 'make dis-configs'.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCHv3 0/2] [redhat] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Simo Sorce (via Email Bridge)
From: Simo Sorce on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125#note_579592828

LGTM for fixing boot issues in FIPS mode.

Acked-by: Simo Sorce s...@redhat.com

(Let's see if the bot is happy now)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCHv3 0/2] [redhat] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Simo Sorce (via Email Bridge)
From: Simo Sorce on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125#note_579591167

LGTM for fixing boot issues in FIPS mode.

Acked-by: Simo Sorce 
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCH 0/3] ark: Set Architecture Level Set to Z14 for s390

2021-05-19 Thread Justin Forbes (via Email Bridge)
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_579494927

I would suggest not changing pending-common.  That is the location for
pre-reviewed, automated defaults.  Nothing should be created there
without a corresponding MR to get that config reviewed and move it to
common.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: [OS-BUILD PATCHv3 0/2] [redhat] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Herbert Xu (via Email Bridge)
From: Herbert Xu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125#note_579476679

Looks good to me.

Acked-by: Herbert Xu 
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv3 2/2] Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov 

Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621

Signed-off-by: Vladis Dronov 

diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CHACHA20=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CHACHA20POLY1305=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CTS=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
@@ -0,0 +1 @@
+CONFIG_CRYPTO_POLY1305=y

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv3 1/2] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov 

Embed crypto algos, modes and templates needed in the FIPS mode

Currently a number of FIPS-allowed algorithms are built as modules or are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms, modes
and templates into a kernel, the same way as CTC, CBC and other algorithms
already do.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov 

diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS 
b/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_XTS=m
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC 
b/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
@@ -1 +1 @@
-CONFIG_CRYPTO_AUTHENC=m
+CONFIG_CRYPTO_AUTHENC=y
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_CCM 
b/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
@@ -1 +1 @@
-CONFIG_CRYPTO_CCM=m
+CONFIG_CRYPTO_CCM=y
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC 
b/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
@@ -1 +1 @@
-CONFIG_CRYPTO_CMAC=m
+CONFIG_CRYPTO_CMAC=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_NULL 
b/redhat/configs/common/generic/CONFIG_CRYPTO_NULL
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_NULL
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_NULL
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_OFB 
b/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
@@ -1 +1 @@
-CONFIG_CRYPTO_OFB=m
+CONFIG_CRYPTO_OFB=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_RSA 
b/redhat/configs/common/generic/CONFIG_CRYPTO_RSA
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_RSA
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_RSA
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3 
b/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
@@ -1 +1 @@
-CONFIG_CRYPTO_SHA3=m
+CONFIG_CRYPTO_SHA3=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_XTS 
b/redhat/configs/common/generic/CONFIG_CRYPTO_XTS
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_XTS
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_XTS

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv3 0/2] [redhat] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125

```
Currently a number of FIPS-allowed algorithms are built as modules or
are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms,
modes
and templates into a kernel, the same way as CTC, CBC and other
algorithms
already do.

The below is a detailed description of a current state and changes
suggested
in this patchset in a readable form:

$ git grep CRYPTO_SHA3
common/generic/CONFIG_CRYPTO_SHA3:CONFIG_CRYPTO_SHA3=m  ###
should be =y

$ git grep CRYPTO_RSA
fedora/generic/CONFIG_CRYPTO_RSA:CONFIG_CRYPTO_RSA=y###
unify, set =y

$ git grep CRYPTO_NULL
fedora/generic/CONFIG_CRYPTO_NULL:CONFIG_CRYPTO_NULL=y  ###
should be common

$ git grep -e
'CRYPTO_\(ECB\|CBC\|CTR\|XTS\|GCM\|CCM\|AUTH\|HMAC\|CMAC\|OFB\|CTS\)'
   ark/generic/CONFIG_CRYPTO_XTS:CONFIG_CRYPTO_XTS=m###
unify, set to =y
fedora/generic/CONFIG_CRYPTO_XTS:CONFIG_CRYPTO_XTS=y###
unify, set to =y
common/generic/CONFIG_CRYPTO_CCM:CONFIG_CRYPTO_CCM=m### set
to =y
common/generic/CONFIG_CRYPTO_AUTHENC:CONFIG_CRYPTO_AUTHENC=m### set
to =y
common/generic/CONFIG_CRYPTO_CMAC:CONFIG_CRYPTO_CMAC=m  ### set
to =y
common/generic/CONFIG_CRYPTO_OFB:CONFIG_CRYPTO_OFB=m### set
to =y

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov 
```
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv2 1/2] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov 

Embed crypto algos, modes and templates needed in the FIPS mode

Currently a number of FIPS-allowed algorithms are built as modules or are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms, modes
and templates into a kernel, the same way as CTC, CBC and other algorithms
already do.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov 

diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS 
b/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_XTS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_XTS=m
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC 
b/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_AUTHENC
@@ -1 +1 @@
-CONFIG_CRYPTO_AUTHENC=m
+CONFIG_CRYPTO_AUTHENC=y
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_CCM 
b/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_CCM
@@ -1 +1 @@
-CONFIG_CRYPTO_CCM=m
+CONFIG_CRYPTO_CCM=y
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC 
b/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_CMAC
@@ -1 +1 @@
-CONFIG_CRYPTO_CMAC=m
+CONFIG_CRYPTO_CMAC=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_NULL 
b/redhat/configs/common/generic/CONFIG_CRYPTO_NULL
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_NULL
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_NULL
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_OFB 
b/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_OFB
@@ -1 +1 @@
-CONFIG_CRYPTO_OFB=m
+CONFIG_CRYPTO_OFB=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_RSA 
b/redhat/configs/common/generic/CONFIG_CRYPTO_RSA
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_RSA
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_RSA
diff a/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3 
b/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
--- a/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_SHA3
@@ -1 +1 @@
-CONFIG_CRYPTO_SHA3=m
+CONFIG_CRYPTO_SHA3=y
diff a/redhat/configs/fedora/generic/CONFIG_CRYPTO_XTS 
b/redhat/configs/common/generic/CONFIG_CRYPTO_XTS
--- a/redhat/configs/fedora/generic/CONFIG_CRYPTO_XTS
+++ b/redhat/configs/common/generic/CONFIG_CRYPTO_XTS

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv2 2/2] Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov 

Revert s390x/zfcpdump part of a9d179c40281 and ecbfddd98621

Signed-off-by: Vladis Dronov 

diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CHACHA20=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CHACHA20POLY1305=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CTS
@@ -0,0 +1 @@
+CONFIG_CRYPTO_CTS=y
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305 
b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
@@ -0,0 +1 @@
+CONFIG_CRYPTO_POLY1305=y

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCHv2 0/2] [redhat] Embed crypto algos, modes and templates needed in the FIPS mode

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1125

```
Currently a number of FIPS-allowed algorithms are built as modules or
are
not enabled in Fedora and ARK. This can result in a panic while booting
in the FIPS mode. Fix this by embedding the FIPS-allowed algorithms,
modes
and templates into a kernel, the same way as CTC, CBC and other
algorithms
already do.

The below is a detailed description of a current state and changes
suggested
in this patchset in a readable form:

$ git grep CRYPTO_SHA3
common/generic/CONFIG_CRYPTO_SHA3:CONFIG_CRYPTO_SHA3=m  ###
should be =y

$ git grep CRYPTO_RSA
fedora/generic/CONFIG_CRYPTO_RSA:CONFIG_CRYPTO_RSA=y###
unify, set =y

$ git grep CRYPTO_NULL
fedora/generic/CONFIG_CRYPTO_NULL:CONFIG_CRYPTO_NULL=y  ###
should be common

$ git grep -e
'CRYPTO_\(ECB\|CBC\|CTR\|XTS\|GCM\|CCM\|AUTH\|HMAC\|CMAC\|OFB\|CTS\)'
   ark/generic/CONFIG_CRYPTO_XTS:CONFIG_CRYPTO_XTS=m###
unify, set to =y
fedora/generic/CONFIG_CRYPTO_XTS:CONFIG_CRYPTO_XTS=y###
unify, set to =y
common/generic/CONFIG_CRYPTO_CCM:CONFIG_CRYPTO_CCM=m### set
to =y
common/generic/CONFIG_CRYPTO_AUTHENC:CONFIG_CRYPTO_AUTHENC=m### set
to =y
common/generic/CONFIG_CRYPTO_CMAC:CONFIG_CRYPTO_CMAC=m  ### set
to =y
common/generic/CONFIG_CRYPTO_OFB:CONFIG_CRYPTO_OFB=m### set
to =y

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1947240
Signed-off-by: Vladis Dronov 
```
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCH] [redhat] Add CONFIG_SYSTEM_REVOCATION_KEYS and _LIST

2021-05-19 Thread Vladis Dronov (via Email Bridge)
From: Vladis Dronov 

[redhat] Add CONFIG_SYSTEM_REVOCATION_KEYS and _LIST

Add CONFIG_SYSTEM_REVOCATION_KEYS and CONFIG_SYSTEM_REVOCATION_LIST options.
Make them disabled since there are no revoked certificates embedded.

Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0e22b47f650
Link: https://gitlab.com/redhat/rhel/src/kernel/rhel-8/-/merge_requests/456
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1893793
Signed-off-by: Vladis Dronov 

diff a/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_KEYS 
b/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_KEYS
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_KEYS
@@ -0,0 +1 @@
+# CONFIG_SYSTEM_REVOCATION_KEYS is not set
diff a/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_LIST 
b/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_LIST
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SYSTEM_REVOCATION_LIST
@@ -0,0 +1 @@
+# CONFIG_SYSTEM_REVOCATION_LIST is not set
diff a/redhat/configs/pending-common/generic/CONFIG_SYSTEM_REVOCATION_LIST 
b/redhat/configs/pending-common/generic/CONFIG_SYSTEM_REVOCATION_LIST
--- a/redhat/configs/pending-common/generic/CONFIG_SYSTEM_REVOCATION_LIST
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_SYSTEM_REVOCATION_LIST:
-# 
-# If set, this allows revocation certificates to be stored in the
-# blacklist keyring and implements a hook whereby a PKCS#7 message can
-# be checked to see if it matches such a certificate.
-# 
-# Symbol: SYSTEM_REVOCATION_LIST [=n]
-# Type  : bool
-# Defined at certs/Kconfig:86
-#   Prompt: Provide system-wide ring of revocation certificates
-#   Depends on: CRYPTO [=y] && SYSTEM_BLACKLIST_KEYRING [=y] && 
PKCS7_MESSAGE_PARSER [=y]=y
-#   Location:
-# -> Cryptographic API (CRYPTO [=y])
-#   -> Certificates for signature checking
-# -> Provide system-wide ring of blacklisted keys 
(SYSTEM_BLACKLIST_KEYRING [=y])
-# 
-# 
-# 
-# CONFIG_SYSTEM_REVOCATION_LIST is not set
diff a/redhat/configs/pending-fedora/generic/CONFIG_SYSTEM_REVOCATION_LIST 
b/redhat/configs/pending-fedora/generic/CONFIG_SYSTEM_REVOCATION_LIST
--- a/redhat/configs/pending-fedora/generic/CONFIG_SYSTEM_REVOCATION_LIST
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_SYSTEM_REVOCATION_LIST:
-# 
-# If set, this allows revocation certificates to be stored in the
-# blacklist keyring and implements a hook whereby a PKCS#7 message can
-# be checked to see if it matches such a certificate.
-# 
-# Symbol: SYSTEM_REVOCATION_LIST [=n]
-# Type  : bool
-# Defined at certs/Kconfig:86
-#   Prompt: Provide system-wide ring of revocation certificates
-#   Depends on: CRYPTO [=y] && SYSTEM_BLACKLIST_KEYRING [=y] && 
PKCS7_MESSAGE_PARSER [=y]=y
-#   Location:
-# -> Cryptographic API (CRYPTO [=y])
-#   -> Certificates for signature checking
-# -> Provide system-wide ring of blacklisted keys 
(SYSTEM_BLACKLIST_KEYRING [=y])
-# 
-# 
-# 
-# CONFIG_SYSTEM_REVOCATION_LIST is not set

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1145
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCH 3/3] configs/ark/s390: set CONFIG_MARCH_Z14 and CONFIG_TUNE_Z15

2021-05-19 Thread Philipp Rudo (via Email Bridge)
From: Philipp Rudo 

configs/ark/s390: set CONFIG_MARCH_Z14 and CONFIG_TUNE_Z15

Optimize ark for newer machines.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1876435
Signed-off-by: Philipp Rudo 

diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z13 
b/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z13
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z13
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_MARCH_Z13=y
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z14 
b/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z14
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z14
@@ -0,0 +1 @@
+CONFIG_MARCH_Z14=y
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z14 
b/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z14
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z14
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_TUNE_Z14=y
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z15 
b/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z15
--- /dev/null
+++ b/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z15
@@ -0,0 +1 @@
+CONFIG_TUNE_Z15=y
diff a/redhat/configs/fedora/generic/s390x/CONFIG_MARCH_Z13 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z13
--- a/redhat/configs/fedora/generic/s390x/CONFIG_MARCH_Z13
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z13
diff a/redhat/configs/fedora/generic/s390x/CONFIG_TUNE_Z14 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z14
--- a/redhat/configs/fedora/generic/s390x/CONFIG_TUNE_Z14
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z14
diff a/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z14 
b/redhat/configs/fedora/generic/s390x/CONFIG_MARCH_Z14
--- a/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z14
+++ b/redhat/configs/fedora/generic/s390x/CONFIG_MARCH_Z14
diff a/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z15 
b/redhat/configs/fedora/generic/s390x/CONFIG_TUNE_Z15
--- a/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z15
+++ b/redhat/configs/fedora/generic/s390x/CONFIG_TUNE_Z15

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCH 2/3] configs/common/s390: Clean up CONFIG_{MARCH,TUNE}_Z*

2021-05-19 Thread Philipp Rudo (via Email Bridge)
From: Philipp Rudo 

configs/common/s390: Clean up CONFIG_{MARCH,TUNE}_Z*

Most of the configs are identical for fedora and ark so move them to
common/generic/s390x.

While at it move the remaining configs in fedora/generic to
fedora/generic/s390x.

Signed-off-by: Philipp Rudo 

diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z10 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z10
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z10
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z10
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z14 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z14
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z14
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z14
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z196 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z196
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z196
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z196
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z900 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z900
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z900
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z900
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z990 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z990
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z990
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z990
diff a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z9_109 
b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z9_109
--- a/redhat/configs/ark/generic/s390x/CONFIG_MARCH_Z9_109
+++ b/redhat/configs/common/generic/s390x/CONFIG_MARCH_Z9_109
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z10 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z10
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z10
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z10
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z13 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z13
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z13
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z13
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z196 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z196
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z196
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z196
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z900 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z900
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z900
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z900
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z990 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z990
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z990
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z990
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z9_109 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z9_109
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_Z9_109
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_Z9_109
diff a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_ZEC12 
b/redhat/configs/common/generic/s390x/CONFIG_TUNE_ZEC12
--- a/redhat/configs/ark/generic/s390x/CONFIG_TUNE_ZEC12
+++ b/redhat/configs/common/generic/s390x/CONFIG_TUNE_ZEC12
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z10 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z10
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z10
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z10 is not set
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z14 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z14
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z14
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z14 is not set
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z196 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z196
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z196
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z196 is not set
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z900 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z900
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z900
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z900 is not set
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z990 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z990
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z990
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z990 is not set
diff a/redhat/configs/fedora/generic/CONFIG_MARCH_Z9_109 
b/redhat/configs/fedora/generic/CONFIG_MARCH_Z9_109
--- a/redhat/configs/fedora/generic/CONFIG_MARCH_Z9_109
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_MARCH_Z9_109 is not set
diff a/redhat/configs/fedora/generic/CONFIG_TUNE_Z10 
b/redhat/configs/fedora/generic/CONFIG_TUNE_Z10
--- a/redhat/configs/fedora/generic/CONFIG_TUNE_Z10
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_TUNE_Z10 is not set

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an 

[OS-BUILD PATCH 1/3] configs/process_configs.sh: make use of dummy-tools

2021-05-19 Thread Philipp Rudo (via Email Bridge)
From: Philipp Rudo 

configs/process_configs.sh: make use of dummy-tools

Using cc-option adds a dependency on the compiler in the configuration
environment. This usually breaks the config creation when the target
architecture is not the host architecture. As a remedy f88717cf44eb
("Temporarily switch TUNE_DEFAULT to y") unset failing configs to their
defaults. In the meantime upstream introduced the scripts/dummy-tools,
which are meant to disable cc-option checks by always returning 'y'.
Make use of the dummy-tools and revert the workaround.

Using the dummy-tools process_configs.sh finds new unset configs. These
are added to pending-common and set to their default.

Signed-off-by: Philipp Rudo 

diff a/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_PATTERN 
b/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_PATTERN
--- /dev/null
+++ b/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_PATTERN
@@ -0,0 +1 @@
+# CONFIG_INIT_STACK_ALL_PATTERN is not set
diff a/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_ZERO 
b/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_ZERO
--- /dev/null
+++ b/redhat/configs/pending-common/generic/CONFIG_INIT_STACK_ALL_ZERO
@@ -0,0 +1 @@
+# CONFIG_INIT_STACK_ALL_ZERO is not set
diff a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_RELR 
b/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_RELR
--- /dev/null
+++ b/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_RELR
@@ -0,0 +1 @@
+CONFIG_RELR=y
diff a/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_DEFAULT 
b/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_DEFAULT
--- a/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_DEFAULT
+++ /dev/null
@@ -1,4 +0,0 @@
-# Broken in commit 5474080a3a0a ("s390/Kconfig: make use of 'depends on
-# cc-option'"); refer to
-# https://lore.kernel.org/lkml/20191209164155.ga78...@dev.jcline.org/
-CONFIG_TUNE_DEFAULT=y
diff a/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_Z14 
b/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_Z14
--- a/redhat/configs/pending-common/generic/s390x/CONFIG_TUNE_Z14
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_TUNE_Z14 is not set
diff a/redhat/configs/process_configs.sh b/redhat/configs/process_configs.sh
--- a/redhat/configs/process_configs.sh
+++ b/redhat/configs/process_configs.sh
@@ -193,11 +193,11 @@ function commit_new_configs()
fi
echo -n "Checking for new configs in $cfg ... "
 
-   make ARCH="$arch" KCONFIG_CONFIG="$cfgorig" listnewconfig >& 
.listnewconfig
+   make ARCH="$arch" CROSS_COMPILE=scripts/dummy-tools/ 
KCONFIG_CONFIG="$cfgorig" listnewconfig >& .listnewconfig
grep -E 'CONFIG_' .listnewconfig > .newoptions
if test -s .newoptions
then
-   make ARCH="$arch" KCONFIG_CONFIG="$cfgorig" 
helpnewconfig >& .helpnewconfig
+   make ARCH="$arch" CROSS_COMPILE=scripts/dummy-tools/ 
KCONFIG_CONFIG="$cfgorig" helpnewconfig >& .helpnewconfig
parsenewconfigs
fi
rm .newoptions
@@ -227,7 +227,7 @@ function process_configs()
fi
echo -n "Processing $cfg ... "
 
-   make ARCH="$arch" KCONFIG_CONFIG="$cfgorig" listnewconfig >& 
.listnewconfig
+   make ARCH="$arch" CROSS_COMPILE=scripts/dummy-tools/ 
KCONFIG_CONFIG="$cfgorig" listnewconfig >& .listnewconfig
grep -E 'CONFIG_' .listnewconfig > .newoptions
if test -n "$NEWOPTIONS" && test -s .newoptions
then
@@ -252,7 +252,7 @@ function process_configs()
 
rm .listnewconfig
 
-   make ARCH="$arch" KCONFIG_CONFIG="$cfgorig" olddefconfig > 
/dev/null || exit 1
+   make ARCH="$arch" CROSS_COMPILE=scripts/dummy-tools/ 
KCONFIG_CONFIG="$cfgorig" olddefconfig > /dev/null || exit 1
echo "# $arch" > "$cfgtmp"
cat "$cfgorig" >> "$cfgtmp"
if test -n "$CHECKOPTIONS"

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


[OS-BUILD PATCH 0/3] ark: Set Architecture Level Set to Z14 for s390

2021-05-19 Thread Philipp Rudo (via Email Bridge)
From: Philipp Rudo on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144

The last commit addresses
https://bugzilla.redhat.com/show_bug.cgi?id=1876435
and is preceded by two cleanups.

The first commit is strictly speaking independent. If requested I can
move it
to a separate MR.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure