Your message dated Sun, 06 Jul 2025 05:19:17 +0000
with message-id <[email protected]>
and subject line Bug#1106035: fixed in zfs-linux 2.3.2-2
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.2-2
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: Sun, 29 Jun 2025 21:54:37 +0800
Source: zfs-linux
Architecture: source
Version: 2.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers
<[email protected]>
Changed-By: Shengqi Chen <[email protected]>
Closes: 1106035
Changes:
zfs-linux (2.3.2-2) unstable; urgency=medium
.
* d/patches: backport some fixes from 2.3.3 upstream release
(closes: #1106035).
Checksums-Sha1:
beff64e438f718a3b4d40e3dc72b3ca556c523d6 3593 zfs-linux_2.3.2-2.dsc
918639cc8768b48cf1459180b003ff0d56e83462 115044 zfs-linux_2.3.2-2.debian.tar.xz
5eeeb124f7167564d406c344ff7070f588d33ed9 16725
zfs-linux_2.3.2-2_amd64.buildinfo
Checksums-Sha256:
4717e09aa12a26af41498837e64921d85b291f0aae8e501e55c82c58a715ace3 3593
zfs-linux_2.3.2-2.dsc
2701c4f4615f1c9325dceb9bce775b5de42a6b89a0e12f508b9d8c7c326b1b2d 115044
zfs-linux_2.3.2-2.debian.tar.xz
54df95ed6e316e452603b1cd62b037d4f409e8bef6768976879110866ce14a5d 16725
zfs-linux_2.3.2-2_amd64.buildinfo
Files:
d6670484ed43cd0c5d752182ed1c2605 3593 contrib/kernel optional
zfs-linux_2.3.2-2.dsc
ba9097afcfa43a0f9d192dc04678b9dd 115044 contrib/kernel optional
zfs-linux_2.3.2-2.debian.tar.xz
1b6e93b2e192da6fed0054f891c1a97e 16725 contrib/kernel optional
zfs-linux_2.3.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+Fg++qmpHzqjSzySzhGnsHs6uUYFAmhqBc8ACgkQzhGnsHs6
uUaDghAAx/W0Vc0BA40po7msEYbwcBAVnU6UM0nHtZYa+kQvtq9QmYca7speWYHF
T2cPjhXbaEqC52aQhr/Uu8bgQvii5SSXWgB8zp/0WDy9pqGe+rQFa5fYaCj2Qw4Z
Yz2QYTIH9XQILjpPPN3l9F8njMI3U5kexjceIqIXR0/3auTJAcqIzIIe9Xl69208
lmVMyNttseJDQCk/23J1raY8twg/4bt+hWDDM5XqgRUeOtux7y53mHVzYMlzsbSD
HkbeG9kYIH2ifsC6+KlucmAnl28Q1vBRKiy0RDPmCvOToP1YYnCB6RG/Q1XGVfzb
u5CHcrTx6N21ecC0qDzmqI6hZo9K5+PCp+uZ4eNYZaaYjtauZZQe0AViX6aCLAUK
REOCuwVxVVbeHb9/ZLF7IGtdV8VoKNx0JoYzUf2AQ/qQY2SQlKN4nI4EGF6nBlaq
P1bzjf287S5jt8Zpr1ywtzdM0IJ8nCtKQvPstYSTZzmixmZSJxzCcwnC9kqU8n9S
s8EdbO+HjxQg+sd1DHKtiJ9xmJZTtDCt49o4N0iMnYNP1XpJpMeOPHwmcyOKto70
YfM/DZFCI2LeGr9/rHgGX5ERpn1cQdthFauOz/yPCrAY8uIeLgOc47TQ1SwG/wKZ
uXrHH1WM7hAhVSdG8zy2wXVl77/v+ALfA0YQn2kGgXRc6ewQP+c=
=LWFw
-----END PGP SIGNATURE-----
pgpl363mV2ygC.pgp
Description: PGP signature
--- End Message ---
