[OS-BUILD PATCH] [redhat] New configs in net/ipv6
by GitLab Bridge on behalf of jmflinuxtx
From: "Justin M. Forbes" <jforbes(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_INET6_ESPINTCP:
Support for RFC 8229 encapsulation of ESP and IKE over
TCP/IPv6 sockets.
If unsure, say N.
Symbol: INET6_ESPINTCP [=n]
Type : bool
Defined at net/ipv6/Kconfig:91
Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> The IPv6 protocol (IPV6 [=y])
-> IPv6: ESP transformation (INET6_ESP [=m])
Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
.../common/generic/CONFIG_INET6_ESPINTCP | 1 +
.../generic/CONFIG_INET6_ESPINTCP | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
diff --git a/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP b/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
new file mode 100644
index 000000000000..1b4ebe140e27
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INET6_ESPINTCP
@@ -0,0 +1 @@
+# CONFIG_INET6_ESPINTCP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP b/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
deleted file mode 100644
index b25df3812966..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INET6_ESPINTCP
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_INET6_ESPINTCP:
-#
-# Support for RFC 8229 encapsulation of ESP and IKE over
-# TCP/IPv6 sockets.
-#
-# If unsure, say N.
-#
-# Symbol: INET6_ESPINTCP [=n]
-# Type : bool
-# Defined at net/ipv6/Kconfig:91
-# Prompt: IPv6: ESP in TCP encapsulation (RFC 8229)
-# Depends on: NET [=y] && INET [=y] && IPV6 [=y] && XFRM [=y] && INET6_ESP [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> TCP/IP networking (INET [=y])
-# -> The IPv6 protocol (IPV6 [=y])
-# -> IPv6: ESP transformation (INET6_ESP [=m])
-# Selects: STREAM_PARSER [=y] && NET_SOCK_MSG [=y] && XFRM_ESPINTCP [=y]
-#
-#
-#
-# CONFIG_INET6_ESPINTCP is not set
--
2.26.2
2 years, 4 months
❌ FAIL: Test report for kernel 5.8.18-200.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.18-200.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=54791894
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
✅ 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 nvme - tcp
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:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ Ethernet drivers sanity
Host 4:
✅ 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:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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
Host 3:
✅ Boot test
✅ stress: stress-ng
🚧 ❌ xfstests - ext4
🚧 ❌ xfstests - xfs
🚧 ❌ 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 ⏱.
2 years, 4 months
Fwd: heads up regarding some v5.10 changes
by Peter Robinson
FYI:
---------- Forwarded message ---------
From: Ard Biesheuvel <ardb(a)kernel.org>
Date: Sat, Oct 31, 2020 at 10:22 AM
Subject: heads up regarding some v5.10 changes
To: <cross-distro(a)lists.linaro.org>, Arnd Bergmann <arnd(a)arndb.de>,
Peter Jones <pjones(a)redhat.com>
Hello all,
Just a note to whomever is subscribed to this list regarding some
changes in v5.10 that may affect distros' kernel deployments:
efivars
-------
efivars is the ancient predecessor to efivarFs, that allows access to
EFI variables via sysfs (but with some restrictions). This has been
deprecated since before ARM even had UEFI support, and it is no longer
going to be enabled going forward. EFI pstore has been rewritten to no
longer rely on it, and on x86, the module is still available, but no
longer gets loaded automatically. On !x86, it is no longer built at
all. As far as I could figure out (and I did ask around as well), this
is highly unlikely to regress anything, and on x86, the module can
still be loaded manually if needed (or enabled as a builtin)
deprecated crypto
-----------------
Some crypto drivers have been made to depend on
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE, which is only available if the
crypto AF_ALG socket API is enabled, as the algorithms are never used
by the kernel itself. However, none of these ciphers are known to be
relied upon by user space either (via AF_ALG), and so I strongly
recommend the distros incorporate
# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE is not set
into their v5.10+ kernel configs so that these deprecated algorithms
are simply dropped from the build (the algos are arc4, tea, khazad,
SEED and anubis, others may follow in the future, e.g., md4/5). Note
that iwd/libell used to rely on the kernel's ecb(arc4) implementation,
but this is no longer the case.
kexec/kdump tools
-----------
To make the kernel's PE/COFF header spec compliant, the stext symbol
will be aligned to 64 KB regardless of the page size the kernel was
built with. As far as I can tell looking at the debian source of the
associated tooling, the symbol value of stext is used to infer the
page size, so this will no longer work.
_______________________________________________
cross-distro mailing list
cross-distro(a)lists.linaro.org
https://lists.linaro.org/mailman/listinfo/cross-distro
2 years, 4 months