Upgrade Linux kernel from 6.6 to 6.12 #2300
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ader1990
temporarily deployed
to
development
GitHub Actions
Inactive
|
ZFS 2.2.5 does not support kernel 6.10, the zfs upgrade patches will be dropped after portage stable update PR gets merged (with 2.2.6 zfs): #2298 |
Test report for 4187.0.0+nightly-20241217-2100 / amd64 arm64Platforms tested : qemu_uefi-amd64 qemu_uefi-arm64 qemu_update-arm64
Diagnostic output for qemu_uefi-arm64, run 1
Diagnostic output for qemu_uefi-arm64, run 1
Diagnostic output for qemu_uefi-amd64, run 5Diagnostic output for qemu_uefi-amd64, run 4Diagnostic output for qemu_uefi-amd64, run 3Diagnostic output for qemu_uefi-amd64, run 2Diagnostic output for qemu_uefi-amd64, run 1
Diagnostic output for qemu_uefi-amd64, run 1
Diagnostic output for qemu_uefi-arm64, run 2Diagnostic output for qemu_uefi-amd64, run 2Diagnostic output for qemu_uefi-arm64, run 1Diagnostic output for qemu_uefi-amd64, run 1
Diagnostic output for qemu_uefi-amd64, run 1
|
2 tasks
jepio
reviewed
Sep 10, 2024
| @@ -36,6 +36,5 @@ IUSE="" | |||
| # local patches overlap with the upstream patch. | |||
| UNIPATCH_LIST=" | |||
| ${PATCH_DIR}/z0001-kbuild-derive-relative-path-for-srctree-from-CURDIR.patch \ | |||
| ${PATCH_DIR}/z0002-revert-pahole-flags.patch \ | |||
There was a problem hiding this comment.
Have you tested this?
When pahole is executed with -j (parallel) then btf metadata order is non-deterministic and the built kernel and modules don't match.
It doesn't have to be a revert, but we need to carry some patch (unless something significant changed).
There was a problem hiding this comment.
definitely, working on it. pahole flags moved to scripts/Makefile.btf, so that needs to be addressed, was working now on a patch.
There was a problem hiding this comment.
We recently updated pahole to a newer version (1.27) that was supposed to be reproducible regardless of how many threads it uses, but dropping the patch didn't work for me.
There was a problem hiding this comment.
Seems like we may still need a kernel patch to pass --btf_features=all,reproducible_build: https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?h=v1.27&id=43bd3efa85656565129063cdd6dd7499e44a7867
There was a problem hiding this comment.
I will test it asap and send it to LKML if it works.
There was a problem hiding this comment.
Added the reproducible_build flag to the pahole params, although I don't like how that addition is done, that file is a beautiful soup and needs some better management.
|
Things like this make me want to wait with an upgrade to 6.10: It takes a couple minor releases on a new stable branch before it is ready to make its way into Flatcar. |
Adding the blocker bug here: https://bugzilla.kernel.org/show_bug.cgi?id=219229 Possible resolution from the bug discussion in the kernel config: CONFIG_TCG_TPM2_HMAC=n |
|
The feature CONFIG_TCG_TPM2_HMAC has been introduced in 6.10 as extra security layer: https://github.com/torvalds/linux/blob/master/drivers/char/tpm/Kconfig#L37 |
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
cce5dc3 to
6dd0a5b
Compare
ader1990
temporarily deployed
to
development
GitHub Actions
Inactive
|
Managed to get the ARM64 image built, but the AMD64 image fails at the initrd/grub stage with error: Full error bellow: |
|
Successful build for the AMD64: |
ader1990
temporarily deployed
to
development
GitHub Actions
Inactive
|
The bpf amd64 |
jepio
reviewed
Sep 12, 2024
...oreos-overlay/sys-kernel/coreos-sources/files/6.10/z0002-pahole-remove-parallel-j-flag.patch
Outdated
Show resolved
Hide resolved
...oreos-overlay/sys-kernel/coreos-sources/files/6.10/z0002-pahole-remove-parallel-j-flag.patch
Outdated
Show resolved
Hide resolved
...oreos-overlay/sys-kernel/coreos-sources/files/6.10/z0002-pahole-remove-parallel-j-flag.patch
Outdated
Show resolved
Hide resolved
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
5595c96 to
4ad039e
Compare
|
@t-lo I observed that from Linux kernel 6.10, there is a change in name of a hyper-v daemon binary - see torvalds/linux@82b0945. Should we leave the same systemd unit name though? I wonder how the https://github.com/microsoft/azurelinux will be doing it (have not seen yet any patch). I am oscillating between this 4ad039e vs changing the name in all places. |
I think we should rename the systemd service to prevent confusion down the road. |
The thing is that the binaries do the same thing / have the same interface, but just internally have a different implementation aka uio_hv_generic. The weird part is that the old implementation is still present, but has build disabled. I will add a new service definition (as it also has a different device path trigger) for the new version, to keep things separate. |
|
The /boot partition is very close to a critical level, 49% already used, leaving around 1.5MB free to use: |
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
04d37b9 to
0d9b839
Compare
ader1990
temporarily deployed
to
development
GitHub Actions
Inactive
ader1990
temporarily deployed
to
development
GitHub Actions
Inactive
|
Note: on AMD64 vmlinuz-a, the build_library/extract-initramfs-from-vmlinuz.sh fails due to the fact now that the scripts finds the corrupted CPIO first. Need to do some more debugging on why this issue happens in the first place (what has changed upstream). |
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
06de6c8 to
f62e9ba
Compare
ader1990
had a problem deploying
to
development
GitHub Actions
Failure
ader1990
changed the title
|
Verified and the securebot patches from https://sources.debian.org/data/main/l/linux/6.12.5-1/debian/patches/features/all/lockdown/ are bitwise the same with the ones from https://sources.debian.org/data/main/l/linux/6.10.6-1~bpo12+1/debian/patches/features/all/lockdown/ (the previous sourced ones) |
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
f2eca1b to
5759d67
Compare
ader1990
force-pushed
the
ader1990/linux_kernel_6_10
branch
from
5759d67 to
582883a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrade Linux kernel from the 6.6.y stable branch to 6.12.y stable branch.
See: flatcar/Flatcar#1527
This PR is mostly to reveal any possible big blockers before getting to the new 6.12 LTS release.
Tested 6.10.y and it works as expected.
Tested 6.11.y and it works as expected.
Now testing 6.12.y.
Testing done
[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.Boot partition size: