Your message dated Thu, 14 Aug 2025 17:09:32 +0000
with message-id <[email protected]>
and subject line Bug#1106035: fixed in zfs-linux 2.3.3-1
has caused the Debian Bug report #1106035,
regarding zfs: Upstream patch for old encryption data corruption bug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1106035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106035
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zfs-dkms
Version: 2.3.2-1
Severity: grave
Tags: upstream patch
Dear Maintainer,
since the release of ZFS 2.0.0 back in 2020, ZFS contains a corruption
bug where snapshots and/or a dataset can get corrupted when using ZFS
encryption, if you're performing a "zfs send" at the same time as making
a snapshot (which can lead to data loss in specific scenarios, which is
why I tagged this as 'grave'; feel free to downgrade if you disagree).
This has been discussed upstream for years at
https://github.com/openzfs/zfs/issues/12014, but since the corruption
wasn't deterministic and it was hard to create a proper test, this was
apparently extremely hard to bisect.
Recently, though, people finally managed to reproduce this issue in a
controlled environment, were able to bisect the bug to merge request
https://github.com/openzfs/zfs/pull/7958.
A proposed fix for the issue is available at
https://github.com/openzfs/zfs/pull/17340. If I'm reading the comments
correctly, then this is clear broken behavior (two functions are called
that should never be called in this way), and even though it's not 100%
certain yet that this is definitely the fix for this long-standing
issue, people are fairly certain it is, and there's already discussions
about backporting it to 2.2.x (https://github.com/openzfs/zfs/pull/17325).
Given that we're in Hard Freeze already, I doubt that zfs-2.3.3 will get
released in time to still make it into trixie.
However, given that A) the fix is extremely simple (two lines of code
changed), B) it fixes a bug that can lead to data loss, C) the current
implementation is definitely wrong, I was wondering if that change can
be added to Debian's package and released as a 2.3.2-2 or similar (and
maybe even backported to bookworm-bpo).
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.3.3-1
Done: Shengqi Chen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
zfs-linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shengqi Chen <[email protected]> (supplier of updated zfs-linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 14 Aug 2025 23:02:14 +0800
Source: zfs-linux
Architecture: source
Version: 2.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers
<[email protected]>
Changed-By: Shengqi Chen <[email protected]>
Closes: 1106035 1106556
Changes:
zfs-linux (2.3.3-1) unstable; urgency=medium
.
* New upstream version 2.3.3 (closes: #1106035, #1106556).
* d/patches: refresh existing patches.
* d/symbols: add symbols in new version, remove vanished ones.
* d/copyright: remove deprecated FSF physical addresses.
Checksums-Sha1:
7c9526723f2eb2bae599e7e0b5931492443344f2 3593 zfs-linux_2.3.3-1.dsc
716bd6cc6bb27e7d7b946d94d2edf79313bc8a45 34360540 zfs-linux_2.3.3.orig.tar.gz
724abd313c22ebeb47a4b30461c2cc2d08619c1c 110588 zfs-linux_2.3.3-1.debian.tar.xz
5986fbc6c128f77a8cbd6bcc85b84102f52f5fb7 16841
zfs-linux_2.3.3-1_amd64.buildinfo
Checksums-Sha256:
80215642e8332b2ba681383fcb99bc17b4c008f0bd615c248372e03b246b3f8b 3593
zfs-linux_2.3.3-1.dsc
844122118f0ea81205a01753bbcb1315330f8967c1f866dcd10155273131f071 34360540
zfs-linux_2.3.3.orig.tar.gz
8f76070b0cce1dd9f4968dd5836511ded00c72c4f5e7db5c917afc4b78226a1d 110588
zfs-linux_2.3.3-1.debian.tar.xz
87e0e53cc948a528ee8f2d52fd9c02d6bcd0467f7e96d250103dc07fc72e85bf 16841
zfs-linux_2.3.3-1_amd64.buildinfo
Files:
cff513d6319919ca4142f991a91ed118 3593 contrib/kernel optional
zfs-linux_2.3.3-1.dsc
16f08cddc449c91e1ff757843c400cc0 34360540 contrib/kernel optional
zfs-linux_2.3.3.orig.tar.gz
8bb518e5a095bef2047e9311a376f1cf 110588 contrib/kernel optional
zfs-linux_2.3.3-1.debian.tar.xz
6fc28e78c6e7d5f1dbe10fa7e2e08db4 16841 contrib/kernel optional
zfs-linux_2.3.3-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+Fg++qmpHzqjSzySzhGnsHs6uUYFAmid+3wACgkQzhGnsHs6
uUYoSxAAptYm1ET7p5eoW4uMi1qcDXvj57aUy5valotK4fikVvR61WywoK8QGRs/
pfAmWTAhBOJUxAf5wtKcFd+Yg4lZqTfhTheRVHQS4ULHj4aqGVr6ZTIFnFi4obVI
ZfxXVQBz0zJKCxNq3agu4xSJNwQi+jaz5gj1d975oWemLRMRVn/niS9E7gBYCwrH
bOr9GcoTkzaxl1zhRqu0YMsgbdC9+3wn+ecTDW9/UqJFG7BoZ2zJHqmUjt23JhzV
qQG1fjauadHYSZ1KEbBjidE+L+HOjcdr8cQdTPmVeUOEgZFWV/Uu1AqZsBM+2UNQ
uKBbPZXFsBLAQLnYjhj5osrVlGTFx+sH6lKdYXPq5/Bjp4KF7lVoG4InydtSXYzV
OJQO7pj35/FUeH4BNcNAAmQuFh9HoObf1oP8B/w/BlpZLu1bIw1RWUg3rWntE9K3
CJCeTT3wjwjjcLwPLuaD+ywjmLIZYeJkT05MWu2Pn7z3bGCsyHNHBjAQkmP9yQRX
azoEEsH0QLXlRPlCu244qhdpiTR2CYNXsw8K2n0LfD7EwzEHpLoUKUDoAmmdUvX0
jsPIkdeyVXsjYggwNlG1GLKqrEjtDb8lLvl5EkuE28jVrun0nWczoU2xkPj2tgag
86HzWSwU1ANZ3NuM3rKChOQG3A9T8Lnh+BGI0r9TF+goXPnIBh4=
=dOkI
-----END PGP SIGNATURE-----
pgpbq59KJQa9P.pgp
Description: PGP signature
--- End Message ---
