Linux kernels 2024-01-29

[alyssais]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[alyssais]

@ofborg test kernel-generic.linux_testing

[vcunat]

BTW, I wonder when the default will move from 6.1 to 6.6. (I couldn't think of a better place to post this.)

[Ma27]

No plans from my side. Also, won't be able to test it for now I'm afraid since I'm still on zfs 2.1 and it seems as if I can't go beyond 6.5 for now.

[RaitoBezarius]

No plans from my side. Also, won't be able to test it for now I'm afraid since I'm still on zfs 2.1 and it seems as if I can't go beyond 6.5 for now.

ZFS 2.1 can go beyond 6.5, but I didn't upstream the patches for that yet (working since 6.7-rc1 to be honest.), upstream has them for 2.2 series but no one bothered backporting them to 2.1 series. My production is running on 6.7 just fine.

[vcunat]

Oh, I guess it makes sense to wait for ZFS to support it, at least if it happens within a couple months.

[RaitoBezarius]

No, there's no need to block on ZFS upstream.

[Ma27]

Oh, I guess it makes sense to wait for ZFS to support it, at least if it happens within a couple months.

I only wanted to state that I likely won't be able to participate in testing before bumping the default (as it was the case on 5.15 -> 6.1 at least).

[alyssais]

Next stable ZFS 2.1.x and 2.2.x will support it. (openzfs/zfs#15761, openzfs/zfs#15748), so given that I'm inclined to wait a little bit.

I don't think we really need to do much(/any) testing — the chances any one tester would run into a showstopper bug are insignificant given how many people will already have been testing it as linux_latest etc.

[github-actions]

Successfully created backport PR for release-23.11:

• [Backport release-23.11] Linux kernels 2024-01-29 #284801

[github-actions]

Git push to origin failed for release-23.11 with exitcode 1

[RaitoBezarius]

Next stable ZFS 2.1.x and 2.2.x will support it. (openzfs/zfs#15761, openzfs/zfs#15748), so given that I'm inclined to wait a little bit.

This gives only the support for the aarch64 SIMD operations, there's a bunch of work to do for 6.7 because of various changes in the API: here's a public list of patches for it #271703.

[alyssais]

This gives only the support for the aarch64 SIMD operations, there's a bunch of work to do for 6.7 because of various changes in the API: here's a public list of patches for it #271703.

But we're talking about 6.6, the LTS.

[RaitoBezarius]

This gives only the support for the aarch64 SIMD operations, there's a bunch of work to do for 6.7 because of various changes in the API: here's a public list of patches for it #271703.

But we're talking about 6.6, the LTS.

Apologies… I confused things.