I wondered why my old bug report has not gotten any attention. Being a
duplicate of this bug didn't help, but at least someone from the
security team marked it as a duplicate of this bug.

BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with
not one single person assigned, that are either marked as new, or
confirmed, just because there were multiple users affected...

Has anyone else, besides me, wondered why they are not even getting
triaged?

We do our due diligence to report these issues. I do my research,
testing try to find answers, and work-around's... That we "can" get past
what is wrong. I keep trying to keep faith in this support system. We
try to make a difference, and do things for the betterment of Ubuntu. It
does not seem sometimes like we are being taken seriously, or being
heard.

What other choices do we have? Compile it ourselves or add it to our own
PPA"s? For actively supported  versions, this seems like it should just
be dealt with right? Especially for LTS.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044657

Title:
  zfs block cloning file system corruption

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  OpenZFS 2.2 reportedly has a bug where block cloning might lead to
  file system corruption and data loss. This was fixed in OpenZFS 2.2.1.

  Original bug report: https://github.com/openzfs/zfs/issues/15526

  and 2.2.1 release notes:
  https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+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

Reply via email to