Yesterday evening, a grave issue was found in stable kernels. Can someone please confirm which pve-kernels are affected?
From Debian micronews:
Due to an issue in ext4 with data corruption in kernel 6.1.64-1, we are pausing the 12.3 image release for today while we attend to fixes. Please do not update any systems at this time, we urge caution for users with UnattendedUpgrades configured. Please see bug# 1057843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
Additional Info from https://lwn.net/Articles/954285/
- Stable kernels < 6.5 are affected if they have 91562895f803 (ext4 commit)
- Kernels >= 6.5 are not affected, as they will _also_ have 936e114a245b6 (iomap commit)
I know that pve-kernel is based on Ubuntu kernels, but I'm not unable to verify, which versions of pve-kernel contain the iomap commit "fixing" the issue.
PS: pve-kernel 6.5.11-7 contains the fix for the ther (ZFS-) data corruption bug. TY @proxmox-team
From Debian micronews:
Due to an issue in ext4 with data corruption in kernel 6.1.64-1, we are pausing the 12.3 image release for today while we attend to fixes. Please do not update any systems at this time, we urge caution for users with UnattendedUpgrades configured. Please see bug# 1057843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
Additional Info from https://lwn.net/Articles/954285/
- Stable kernels < 6.5 are affected if they have 91562895f803 (ext4 commit)
- Kernels >= 6.5 are not affected, as they will _also_ have 936e114a245b6 (iomap commit)
I know that pve-kernel is based on Ubuntu kernels, but I'm not unable to verify, which versions of pve-kernel contain the iomap commit "fixing" the issue.
PS: pve-kernel 6.5.11-7 contains the fix for the ther (ZFS-) data corruption bug. TY @proxmox-team