Comment 48 for bug 2044657

On Fri, 8 Dec 2023 at 23:35, Steve Langasek <email address hidden> wrote:
>
> zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium
>
> * New upstream release. LP: #2044657
> - Address potential data corruption
>
> I'm assuming the plan for fixing it on earlier releases does not involve
> updating to 2.2.2.
>
> And this does not fall under a hardware enablement exception. AND there
> are packaging changes under debian/.
>
> The diff for this new upstream release is 9kloc. I would expect a
> cherry-picked fix here for mantic, not a full upstream backport - just
> as will be required for releases prior to mantic.

My plan was to do updates as follows:
- upgrade to 2.2.2 for mantic
- upgrade to 2.1.14 for jammy (to cover this issue, but also potential
straight line speculation fixes)
- cherry-pick of individual bug fix for focal and earlier

I also do not understand why I ended up maintaining any of zfs-linux
anymore btw. Especially the userspace side of things. I am happy to
SRU just the kernel code changes alone, and let foundations handle the
zfs userspace fixes.

Separately, do note that lxd snap builds and vendors the full multiple
zfs userspace tooling. So i'm not sure there is any stability value in
not taking the full point releases for the userspace tooling changes
in the classic ubuntu release - or try to untangle them.

Regards,

Dimitri.