[OS-BUILD PATCH 0/0] Fedora: updates for 5.12
by pbrobinson (via Email Bridge)
From: pbrobinson on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/952
NOTE: Truncated patchset due to missing @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the merge request to
retrigger sending the emails.
First patch removes a bunch of options that were removed from the
upstream kernel, in particular a bunch of old dead arm socs plus intel
MID and associated drivers we never enabled anyway.
Second is updates for 5.12 merge window, primarily arm based but a few
x86 and generic updates.
Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com>
3Β years
β FAIL: Test report for kernel 5.11.3-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.3-50.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=63146329
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
s390x:
β LTP
π₯ stress: stress-ng
ppc64le:
β LTP
aarch64:
β LTP
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
π§ β
xfstests - btrfs
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
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
β 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: lvm device-mapper test
π§ β
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
π§ β
Storage blktests
π§ β
Storage nvme - tcp
π§ β
Storage: swraid mdadm raid_module test
π§ π₯ stress: stress-ng
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:
β‘ 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
π§ β
xfstests - btrfs
π§ β
xfstests - nfsv4.2
π§ β xfstests - cifsv3.11
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β‘β‘β‘ Storage block - queue scheduler test
π§ β‘β‘β‘ Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years
β FAIL: Test report for kernel 5.11.3-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.3-50.fc33
COPR build ID: 2057255
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
aarch64:
β 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
β
selinux-policy: serge-testsuite
β
storage: software RAID testing
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
IPMI driver test
π§ β
IPMItool loop stress test
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
Host 2:
β
Boot test
β
ACPI table test
β
ACPI enabled test
β LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
β
Networking bridge: sanity
β
Networking socket: fuzz
β
Networking: igmp conformance test
β
Networking route: pmtu
β
Networking route_func - local
β
Networking route_func - forward
β
Networking TCP: keepalive test
β
Networking UDP: socket
β
Networking tunnel: geneve basic test
β
Networking tunnel: gre basic
β
L2TP basic test
β
Networking tunnel: vxlan basic
β
Networking ipsec: basic netns - transport
β
Networking ipsec: basic netns - tunnel
β
Libkcapi AF_ALG test
β
pciutils: update pci ids test
β
ALSA PCM loopback test
β
ALSA Control (mixer) Userspace Element test
β
storage: SCSI VPD
β
trace: ftrace/tracer
π§ β
i2c: i2cdetect sanity
π§ β
CIFS Connectathon
π§ β
POSIX pjd-fstest suites
π§ β
Firmware test suite
π§ β
jvm - jcstress tests
π§ β
Memory function: kaslr
π§ β
Ethernet drivers sanity
π§ β
Networking cki netfilter test
π§ β audit: audit testsuite 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 β±.
3Β years
β FAIL: Test report for kernel 5.11.3-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.3-50.fc33
COPR build ID: 2057255
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
aarch64:
β 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
β
ACPI enabled test
β LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
β
Networking bridge: sanity
β
Networking socket: fuzz
β
Networking: igmp conformance test
β
Networking route: pmtu
β
Networking route_func - local
β
Networking route_func - forward
β
Networking TCP: keepalive test
β
Networking UDP: socket
β
Networking tunnel: geneve basic test
β
Networking tunnel: gre basic
β
L2TP basic test
β
Networking tunnel: vxlan basic
β
Networking ipsec: basic netns - transport
β
Networking ipsec: basic netns - tunnel
β
Libkcapi AF_ALG test
β
pciutils: update pci ids test
β
ALSA PCM loopback test
β
ALSA Control (mixer) Userspace Element test
β
storage: SCSI VPD
β
trace: ftrace/tracer
π§ β
i2c: i2cdetect sanity
π§ β
CIFS Connectathon
π§ β
POSIX pjd-fstest suites
π§ β
Firmware test suite
π§ β
jvm - jcstress tests
π§ β
Memory function: kaslr
π§ β
Ethernet drivers sanity
π§ β
Networking cki netfilter test
π§ β audit: audit testsuite test
Host 2:
β
Boot test
β
selinux-policy: serge-testsuite
β
storage: software RAID testing
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
IPMI driver test
π§ β
IPMItool loop stress test
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in lib/Kconfig.debug
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_DEBUG_IRQFLAGS:
Enables checks for potentially unsafe enabling or disabling of
interrupts, such as calling raw_local_irq_restore() when interrupts
are enabled.
Symbol: DEBUG_IRQFLAGS [=n]
Type : bool
Defined at lib/Kconfig.debug:1427
Prompt: Debug IRQ flag manipulation
Location:
-> Kernel hacking
Selected by [n]:
- DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n]
---
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS
@@ -0,0 +1 @@
+# CONFIG_DEBUG_IRQFLAGS is not set
diff a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS
--- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DEBUG_IRQFLAGS:
-#
-# Enables checks for potentially unsafe enabling or disabling of
-# interrupts, such as calling raw_local_irq_restore() when interrupts
-# are enabled.
-#
-# Symbol: DEBUG_IRQFLAGS [=n]
-# Type : bool
-# Defined at lib/Kconfig.debug:1427
-# Prompt: Debug IRQ flag manipulation
-# Location:
-# -> Kernel hacking
-# Selected by [n]:
-# - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n]
-#
-#
-#
-# CONFIG_DEBUG_IRQFLAGS is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/912
3Β years
β FAIL: Test report for kernel 5.10.20-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.20-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=63067719
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
s390x:
β LTP
ppc64le:
β LTP
aarch64:
β LTP
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:
β‘ 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
π§ β
xfstests - btrfs
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
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: lvm device-mapper test
π§ β
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
π§ β
Storage blktests
π§ β
Storage nvme - tcp
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
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:
β‘ 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
π§ β
xfstests - btrfs
π§ β
xfstests - nfsv4.2
π§ β
xfstests - cifsv3.11
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β‘β‘β‘ Storage block - queue scheduler test
π§ β‘β‘β‘ Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years
[OS-BUILD PATCH] [redhat] Provide CONFIG_X86_SGX for x86_64 only
by Vladis Dronov (via Email Bridge)
From: Vladis Dronov <vdronov(a)redhat.com>
[redhat] Provide CONFIG_X86_SGX for x86_64 only
SGX is officially x86_64-only and config X86_SGX depends on X86_64 in Kconfig.
Link: https://github.com/intel/linux-sgx/#prerequisites
Signed-off-by: Vladis Dronov <vdronov(a)redhat.com>
diff a/redhat/configs/common/generic/CONFIG_X86_SGX b/redhat/configs/common/generic/x86/x86_64/CONFIG_X86_SGX
--- a/redhat/configs/common/generic/CONFIG_X86_SGX
+++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_X86_SGX
diff a/redhat/configs/fedora/generic/CONFIG_X86_SGX b/redhat/configs/fedora/generic/CONFIG_X86_SGX
--- a/redhat/configs/fedora/generic/CONFIG_X86_SGX
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_X86_SGX:
-#
-# Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
-# that can be used by applications to set aside private regions of code
-# and data, referred to as enclaves. An enclave's private memory can
-# only be accessed by code running within the enclave. Accesses from
-# outside the enclave, including other enclaves, are disallowed by
-# hardware.
-#
-# If unsure, say N.
-#
-# Symbol: X86_SGX [=n]
-# Type : bool
-# Defined at arch/x86/Kconfig:1937
-# Prompt: Software Guard eXtensions (SGX)
-# Depends on: X86_64 [=y] && CPU_SUP_INTEL [=y] && CRYPTO [=y]=y && CRYPTO_SHA256 [=y]=y
-# Location:
-# -> Processor type and features
-# Selects: SRCU [=y] && MMU_NOTIFIER [=y]
-#
-#
-#
-CONFIG_X86_SGX=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/947
3Β years
[OS-BUILD PATCH] Revert "ARM: fix __get_user_check() in case
uaccess_* calls
are not inlined"
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
Revert "ARM: fix __get_user_check() in case uaccess_* calls are not inlined"
This reverts commit 80660062260dec4bdca9540922577542c16145e8.
This was v1 of the patch posted upstream:
https://lore.kernel.org/patchwork/patch/1132459/
A second version was sent after it:
https://patchwork.kernel.org/project/linux-arm-kernel/patch/2019100108370...
And it is the v2 the one which really was integrated upstream through
this commit:
...
commit 851140ab0d083c78e5723a8b1cbd258f567a7aff
Author: Masahiro Yamada <yamada.masahiro(a)socionext.com>
Date: Wed Oct 2 11:28:02 2019 +0100
ARM: 8908/1: add __always_inline to functions called from __get_user_check()
...
Thus revert the old version which was applied to ARK and shouldn't be
needed anymore since the other version is already upstream.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/arch/arm/include/asm/uaccess.h b/arch/arm/include/asm/uaccess.h
--- a/arch/arm/include/asm/uaccess.h
+++ b/arch/arm/include/asm/uaccess.h
@@ -195,12 +195,11 @@ extern int __get_user_64t_4(void *);
#define __get_user_check(x, p) \
({ \
unsigned long __limit = current_thread_info()->addr_limit - 1; \
- unsigned int __ua_flags = uaccess_save_and_enable(); \
register typeof(*(p)) __user *__p asm("r0") = (p); \
register __inttype(x) __r2 asm("r2"); \
register unsigned long __l asm("r1") = __limit; \
register int __e asm("r0"); \
- unsigned int __err; \
+ unsigned int __ua_flags = uaccess_save_and_enable(); \
switch (sizeof(*(__p))) { \
case 1: \
if (sizeof((x)) >= 8) \
@@ -228,10 +227,9 @@ extern int __get_user_64t_4(void *);
break; \
default: __e = __get_user_bad(); break; \
} \
- __err = __e; \
- x = (typeof(*(p))) __r2; \
uaccess_restore(__ua_flags); \
- __err; \
+ x = (typeof(*(p))) __r2; \
+ __e; \
})
#define get_user(x, p) \
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/941
3Β years
Re: Building custom kernels
by Julian Sikorski
W dniu 27.02.2021 oΒ 20:59, Julian Sikorski pisze:
> Hi,
>
> I am trying to test some Renoir s2idle patches [1]. It appears that
> Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What
> I tried is adding the patches to the fedora-5.11 branch and running make
> dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE:
>
> Processing
> /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config
> ... Error: Mismatches found in configuration files
> Found CONFIG_INIT_STACK_NONE=y after generation, had
> CONFIG_INIT_STACK_NONE=is not set in Source tree
> make[1]: *** [Makefile:145: dist-configs-check] BΕΔ
d 1
>
> Is this expected? Is there a better way of testing patches on Fedora
> kernels? Thanks for the help in advance.
>
> Best regards,
> Julian
>
> [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230
> [2] https://gitlab.com/cki-project/kernel-ark
Hi,
the same keeps happening if I try to merge os-build into agdf5 tree or
even if I try to make srpm in the ark-latest branch. Is this normal?
Best regards,
Julian
3Β years