The kernel config can affect btf generation, and we need btf information
to match between the two builds otherwise modules don't load. Accomplish
that by including an empty user specified initramfs in the vmlinux built
by coreos-modules. This vmlinux file is only used as a base for btf
generation, and is discarded after the build.
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
This patch causes btf mismatches between coreos-kernel and
coreos-modules, which prevents modules from being loaded.
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
CLEANCACHE config was dropped in commit
0a4ee518185e902758191d968600399f3bc2be31 ("mm: remove cleancache").
EFI_VARS config was dropped in commit
0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 ("efi: vars: Remove
deprecated 'efivars' sysfs interface").
DEBUG_INFO config became a config that is selected when kernel debug
info option other than "None" was selected. There are "toolchain
default", "dwarf4" and "dwarf5" choices. Picking "toolchain default"
as it was the default used in 5.15.
FRONTSWAP config was hidden and is normally selected by ZSWAP
config. We don't enable ZSWAP so drop FRONTSWAP.
MEMCG_SWAP config was dropped in commit
e55b9f96860f6c6026cff97966a740576285e07b ("mm: memcontrol: drop dead
CONFIG_MEMCG_SWAP config symbol"). It effectively meant MEMCG && SWAP,
which are enabled by us explicitly and implicitly, respectively.
NFT_COUNTER config was dropped in commit
023223dfbfb34fcc9b7dd41e21fbf9a5d5237989 ("netfilter: nf_tables: make
counter support built-in"). As the title says, this functionality is
built-in now.
VXGE was dropped in commit f05643a0f60bf67c09a5276b81258b845b0c73b4
("eth: remove neterion/vxge"). Looks like the driver was completely
dropped, because it was unmaintained.
ARCH_BCM2835 and ARCH_BCM_IPROC configs can be enabled only if
menuconfig ARCH_BCM is enabled, so enable ARCH_BCM too then. It's a
result of some reorganization in commit
96796c914b841a7658e9617b1325175b4d02c574 ("arm64: Kconfig.platforms:
Re-organized Broadcom menu").
ARM64_CRYPTO config was dropped in commit
4a329fecc9aaebb27a53fa7abfa53bbc2ee42f3f ("crypto: Kconfig - submenus
for arm and arm64"). Crypto algos can be selected without this config
now.
Linux 6.1.x is the line of LTS kernel releases, so switch to it.
Dropped the already-merged patches for hyperv on arm64.
The patch for avoiding failures with new compilers is not necessary
any more as the build failues are already fixed.
This is a kinda-sorta sync, because Gentoo has already dropped docker
20.x.y at 20.10.22, whereas we have 20.10.24. I updated our ebuild
based on the older version of Gentoo's and adapted the dependency
versions to ones mentioned on moby github page. The reason behind this
"syncing" is to pull in changes in the kernel config changes as there
are changes relevant to kernel 6.1.
* Update coreos-cloudinit to latest commit
The latest commit sets the short form hostname that gets fetched from
the metadata provider instead of the FQDN.
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
Co-authored-by: Kai Lüke <pothos@users.noreply.github.com>
It's from Gentoo commit e32772476e61578dd91229d77b82f56822857d92.
It needed an update because the old version failed to build with the
new version of the readline library.
The package will take over the symlink creation from the
sys-apps/baselayout package for the following reasons:
- We will use the new location of the bash files as targets for the
symlinks (`/usr/share/flatcar/etc/skel/…`).
- This package makes sure that the symlinks won't dangle.
- `/usr/share/flatcar/etc` does not exist in GCE OEM ACI image because
we don't move `/etc` to `/usr/share/flatcar/etc` (actually, `/etc`
gets completely removed) when building this image. It makes bash
symlinks in core home directory to dangle and thus fail the rootfs
check that happens right after installing the
`coreos-base/coreos-oem-gce` package. Using the old location for the
bash symlinks (that'd be `/usr/share/skel`) wouldn't help, because
the files there also became symlinks, and they are dangling too.
This can't fix it in the manglefs script because it's invoked too
late, after the rootfs check. I decided to move the core home bash
symlink creation to `coreos-base/misc-files` as this package won't
be installed in ACI image.
The new coreos-base/misc-files package will contain the compatibility
symlinks and other files we added as modifications to Gentoo
ebuilds. Now we will be moving the app-shells/bash package to
portage-stable, so move our bashrc snippet and symlink creation to the
new package.
The temporary /etc backup created during emerging packages should only
contain empty files that will make sure that the symlinks pointing to
files within the /etc backup won't dangle at any time.
