Source: linux Version: 4.19.20-1 Severity: critical Tags: upstream patch Justification: causes serious data loss
Hi. Apparently there was a longer existing data corruption bug in btrfs[0], AFAIU it happened when compression was used together with holes in data and there was *no* recognition by checksumming. Seems some movement got into this the last days and a patch[1] may have been found fixing the issue. Due to potential silent data corruptpion it makes perhaps sense to cherry pick that fix (maybe waiting for confirmation from upstream whether it's the final one) instead of waiting for it being released in some upcoming stable release? Cheers, Chris. [0] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85407.html [1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85492.html -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
