Linux kernel updates 2023-08-16#249636
Merged
Ma27 merged 15 commits intoNixOS:masterfrom Aug 17, 2023
Merged
Conversation
K900
approved these changes
Aug 16, 2023
Contributor
K900
left a comment
K900
left a comment
There was a problem hiding this comment.
Diff LGTM, you'll probably be done testing by tomorrow but if not I can run-test.
ofborg
bot
requested review from
NeQuissimus,
TredwellGit,
alyssais and
thoughtpolice
ofborg
bot
added
11.by: package-maintainer
fabianhjr
approved these changes
Aug 17, 2023
Member
fabianhjr
left a comment
fabianhjr
left a comment
There was a problem hiding this comment.
Built and booted into 6.4.10-hardened1
Contributor
|
Successfully created backport PR for |
1 task
Ma27
added a commit
to Ma27/nixpkgs
that referenced
this pull request
Aug 19, 2023
On NixOS#249636 I had to manually run the updaters for hardened & libre kernels. The cause was that `update-rt.sh` suddenly broke. Because I didn't want to inhibit other kernel updates because of a rather niche variant, I decided to move forward temporarily and take care of it later. One issue was that the script failed silently, i.e. I only saw that the script terminated early from my prompt. This is fixed now by making each niche kernel updater print its exit code code if it failed. Also, errors are allowed, i.e. a broken `update-rt.sh` doesn't block `hardened/update.py` etc.. The issue itself is rather simple. When I updated the kernels in NixOS#249636, the sha256sums.asc for rt kernels[1] looked like this: 199bbb0cdb97ead22732473b95c8b2e8da62dfd71bde2339163119fb537a2b7c patch-6.1.38-rt13-rc1.patch.gz a1af54f6987e96de06cad0a3226c5b5a992b60df084a904b6b94ea247fb46027 patch-6.1.38-rt13-rc1.patch.xz 7bb68561787e46e3c433d9b514373ce368d587ac459b91df41934e70280d008f patches-6.1.38-rt13-rc1.tar.gz ee65336dd6ae0be398796e7b75291918811a23e10121dc09bd84b244b12402fa patches-6.1.38-rt13-rc1.tar.xz However, the script itself skips any RC versions of the realtime patches, so no releases were usable and the script failed. It's probably possible to use the overview over all releases instead[2], however that'd complicate the script notably. Anyways, since RT kernels don't bump to each patch-level release, I don't think it hurts too much if such an update is slightly more delayed. However if we want to fix this, I'd prefer this to be fixed by folks who care more about rt kernels than I do. [1] https://kernel.org/pub/linux/kernel/projects/rt/6.1/sha256sums.asc [2] https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/6.1/older/sha256sums.asc
12 tasks
github-actions bot
pushed a commit
that referenced
this pull request
Aug 20, 2023
On #249636 I had to manually run the updaters for hardened & libre kernels. The cause was that `update-rt.sh` suddenly broke. Because I didn't want to inhibit other kernel updates because of a rather niche variant, I decided to move forward temporarily and take care of it later. One issue was that the script failed silently, i.e. I only saw that the script terminated early from my prompt. This is fixed now by making each niche kernel updater print its exit code code if it failed. Also, errors are allowed, i.e. a broken `update-rt.sh` doesn't block `hardened/update.py` etc.. The issue itself is rather simple. When I updated the kernels in #249636, the sha256sums.asc for rt kernels[1] looked like this: 199bbb0cdb97ead22732473b95c8b2e8da62dfd71bde2339163119fb537a2b7c patch-6.1.38-rt13-rc1.patch.gz a1af54f6987e96de06cad0a3226c5b5a992b60df084a904b6b94ea247fb46027 patch-6.1.38-rt13-rc1.patch.xz 7bb68561787e46e3c433d9b514373ce368d587ac459b91df41934e70280d008f patches-6.1.38-rt13-rc1.tar.gz ee65336dd6ae0be398796e7b75291918811a23e10121dc09bd84b244b12402fa patches-6.1.38-rt13-rc1.tar.xz However, the script itself skips any RC versions of the realtime patches, so no releases were usable and the script failed. It's probably possible to use the overview over all releases instead[2], however that'd complicate the script notably. Anyways, since RT kernels don't bump to each patch-level release, I don't think it hurts too much if such an update is slightly more delayed. However if we want to fix this, I'd prefer this to be fixed by folks who care more about rt kernels than I do. [1] https://kernel.org/pub/linux/kernel/projects/rt/6.1/sha256sums.asc [2] https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/6.1/older/sha256sums.asc (cherry picked from commit ccf0c5b)
CHN-beta
pushed a commit
to CHN-beta/nixpkgs
that referenced
this pull request
Aug 26, 2023
partial revert of f371975 Revert "linuxManualConfig: restore functionality of isModular and buildDTBs" This reverts commit 284d76e. Revert "lib/systems: strip kernel to avoid reference cycles" This reverts commit 2458c94. Revert "linuxManualConfig: set badPlatforms" This reverts commit 5c5e5e2. Revert "linux.configfile: remove unused kernelTarget attr" This reverts commit 01b3642. Revert "linuxManualConfig: always depend on ubootTools" This reverts commit e5e02f3. Revert "linux: default stdenv.hostPlatform.linux-kernel" This reverts commit febe477. Revert "linux: manual-config: use a non-random path for $buildRoot" This reverts commit a695425. Revert "linuxManualConfig: fix inaccurate FIXME comment" This reverts commit 4d15632. Revert "linuxManualConfig: get rid of drvAttrs" This reverts commit f521f46. Revert "linuxManualConfig: install GDB scripts" This reverts commit d57568f. Revert "linuxManualConfig: use the default make target" This reverts commit 41f788b. Revert "linuxManualConfig: unpack directly into $dev" This reverts commit 7de3f08. Revert "linuxManualConfig: don't build inside source tree" This reverts commit d75cff2. kernel: fix passthru.tests NixOS#191540 indirectly broke kernel passthru.tests; calling the testsForLinuxPackages and testsForKernel functions with some args intended for some other exposed test-internal function. Organise the passed-through functions under `passthru` to prevent this from happening. linuxPackages_testing.perf: fix patchShebang Without the change `perf` build fails as: $ nix build --no-link -f. linuxPackages_testing.perf -L build flags: SHELL=/nix/store/p6dlr3skfhxpyphipg2bqnj52999banh-bash-5.2-p15/bin/bash prefix=\$\(out\) WERROR=0 ASCIIDOC8=1 O=\$\(buildRoot\) CC=/nix/store/bxic6j2whyg3z4h2x3xjyqgp7fl83bnp-gcc-wrapper-12.3.0/bin/cc HOSTCC=/nix/store/bxic6j2whyg3z4h2x3xjyqgp7fl83bnp-gcc-wrapper-12.3.0/bin/cc HOSTLD=/nix/store/kcp78dk7h5gcs7d4qss7rbz3skxhzdnn-binutils-wrapper-2.40/bin/ld ARCH=x86_64 NO_GTK2=1 BUILD: Doing 'make -j16' parallel build HOSTCC fixdep.o HOSTLD fixdep-in.o LINK fixdep make[1]: ./check-headers.sh: No such file or directory make[1]: *** [Makefile.perf:241: sub-make] Error 127 make: *** [Makefile:70: all] Error 2 This started happening because upstream linux commit torvalds/linux@d674838 changed shebang from /bin/sh to /bin/bash. Let's retroactively switch all `perf` releases to shell interpreter from store. linux: 4.14.320 -> 4.14.321 linux: 4.19.289 -> 4.19.290 linux: 5.10.188 -> 5.10.189 linux: 5.15.124 -> 5.15.125 linux: 5.4.251 -> 5.4.252 linux: 6.1.43 -> 6.1.44 linux: 6.4.8 -> 6.4.9 linux: disable KUnit (NixOS#247826) linux_testing: 6.5-rc3 -> 6.5-rc5 rc5: https://lwn.net/Articles/940617/ rc4: https://lwn.net/Articles/939684/ linux: 4.14.321 -> 4.14.322 linux: 4.19.290 -> 4.19.291 linux: 5.10.189 -> 5.10.190 linux: 5.4.252 -> 5.4.253 linux: 6.1.44 -> 6.1.45 linux: 6.4.9 -> 6.4.10 linux-rt_5_15: 5.15.119-rt65 -> 5.15.125-rt66 linux: 5.15.125 -> 5.15.126 linux: disable KUNIT only at 5.5 and later `KUNIT` knob was added around 5.5 release: torvalds/linux@914cc63 linux_xanmod: 6.1.43 -> 6.1.45 linux_xanmod_latest: 6.4.8 -> 6.4.10 linux: 4.14.322 -> 4.14.323 linux: 4.19.291 -> 4.19.292 linux: 5.10.190 -> 5.10.191 linux: 5.15.126 -> 5.15.127 linux: 5.4.253 -> 5.4.254 linux: 6.1.45 -> 6.1.46 linux: 6.4.10 -> 6.4.11 linux_latest-libre: 19337 -> 19386 linux/hardened/patches/4.14: 4.14.320-hardened1 -> 4.14.322-hardened1 linux/hardened/patches/4.19: 4.19.289-hardened1 -> 4.19.291-hardened1 linux/hardened/patches/5.10: 5.10.188-hardened1 -> 5.10.190-hardened1 linux/hardened/patches/5.15: 5.15.123-hardened1 -> 5.15.126-hardened1 linux/hardened/patches/5.4: 5.4.251-hardened1 -> 5.4.253-hardened1 linux/hardened/patches/6.1: 6.1.42-hardened1 -> 6.1.45-hardened1 linux/hardened/patches/6.4: 6.4.7-hardened1 -> 6.4.10-hardened1 linux_xanmod: 6.1.45 -> 6.1.46 linux_xanmod_latest: 6.4.10 -> 6.4.11 linux-rt_6_1: 6.1.33-rt11 -> 6.1.46-rt13 linux: make main update script slightly more robust On NixOS#249636 I had to manually run the updaters for hardened & libre kernels. The cause was that `update-rt.sh` suddenly broke. Because I didn't want to inhibit other kernel updates because of a rather niche variant, I decided to move forward temporarily and take care of it later. One issue was that the script failed silently, i.e. I only saw that the script terminated early from my prompt. This is fixed now by making each niche kernel updater print its exit code code if it failed. Also, errors are allowed, i.e. a broken `update-rt.sh` doesn't block `hardened/update.py` etc.. The issue itself is rather simple. When I updated the kernels in NixOS#249636, the sha256sums.asc for rt kernels[1] looked like this: 199bbb0cdb97ead22732473b95c8b2e8da62dfd71bde2339163119fb537a2b7c patch-6.1.38-rt13-rc1.patch.gz a1af54f6987e96de06cad0a3226c5b5a992b60df084a904b6b94ea247fb46027 patch-6.1.38-rt13-rc1.patch.xz 7bb68561787e46e3c433d9b514373ce368d587ac459b91df41934e70280d008f patches-6.1.38-rt13-rc1.tar.gz ee65336dd6ae0be398796e7b75291918811a23e10121dc09bd84b244b12402fa patches-6.1.38-rt13-rc1.tar.xz However, the script itself skips any RC versions of the realtime patches, so no releases were usable and the script failed. It's probably possible to use the overview over all releases instead[2], however that'd complicate the script notably. Anyways, since RT kernels don't bump to each patch-level release, I don't think it hurts too much if such an update is slightly more delayed. However if we want to fix this, I'd prefer this to be fixed by folks who care more about rt kernels than I do. [1] https://kernel.org/pub/linux/kernel/projects/rt/6.1/sha256sums.asc [2] https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/6.1/older/sha256sums.asc
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description of changes
Update all kernels to the latest versions available.
Still a draft until I'm done with testing everything.
Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)