@xyv41: As mentioned in the last comment, the fix is only a cherry-pick so the version will go from 2.1.5-1ubuntu6~22.04.2 to 2.1.5-1ubuntu6~22.04.3 because upgrading to 2.1.14 would bear the risk that other bugs might get fixed, too.
Regarding the release date: for mantic it took about 7 days from verification until release. I don’t know if that's an automated process, but in that case the fix should go out in the next few days. On the other hand, in post #73 it says that the SRU-Team has been unsubscribed from this bug-report, so maybe they don’t even know that the verification for jammy has been completed and the fix will just get stalled. Additionally, even when (or if?) the committed package gets released, this only affects the userland tools as well as the dkms-build kernel modules. If you (like 99,9% of all Ubuntu users) use the pre-bundled kernel module, then this also needs an update of the kernel package as well. To give you an idea: The fix for mantic was committed on February, 2nd and released on the 12th. However, it is still not included in the current kernel package (6.5.0.17.19) nor in the -proposed package (6.5.0.25.25) which is yet to be released. So based on the recent update cycles I suspect it will not reach the end-user until mid of march (for matic!!!). Therefore, I am expecting that it will be at least one more month (more likely 6 weeks) or so until the jammy fix reaches the end-user. Then we will have a fix found (December, 1st) to fix released time of around 5 months. Quite a good result for a one-line-Hotfix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Jammy: Fix Committed Status in zfs-linux source package in Lunar: Won't Fix Status in zfs-linux source package in Mantic: Fix Released Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). * In the absence of the upgrade a cherry-pick will address this particular popular issue alone - without addressing other issues w.r.t. Redbleed / SLS, bugfixes around trim support, and other related improvements that were discovered and fixed around the same time as this popular issue. [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code- paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but only makes it stronger and not weaker, thus if it were incorrect, likely only performance would be impacted (and it is unlikely to be incorrect given upstream reviews and attention to data corruption issues; also, there are no additional changes to that function upstream) [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
