Bug#1110679: linux: btrfs data corruption bug since 6.15.3

[Salvatore Bonaccorso <carnil@debian.org>]

Control: tags -1 + upstream fixed-upstream
Control: forwarded -1 https://lore.kernel.org/linux-btrfs/fce139db-4458-4788-bb97-c29acf6cb1df@cachyos.org/ https://lore.kernel.org/linux-btrfs/lh4W-Lwc0Mbk-QvBhhQyZxf6VbM3E8VtIvU3fPIQgweP_Q1n7wtlUZQc33sYlCKYd-o6rryJQfhHaNAOWWRKxpAXhM8NZPojzsJPyHMf2qY=@protonmail.com/#t https://lore.kernel.org/linux-btrfs/598ecc75-eb80-41b3-83c2-f2317fbb9864@gmail.com/

Hi,

On Sat, Aug 09, 2025 at 11:16:21PM +0200, Christoph Anton Mitterer wrote:
> Source: linux
> Version: 6.15.3-1~exp1
> Severity: critical
> Justification: causes serious data loss
> 
> Hey.
> 
> Since trixie is out now I figured you might sooner or later
> push a newer kernel to unstable...
> 
> Thus a heads up that a data corruption bug has been found in btrfs,
> introduced around 6.15.3, and fixed in commit
> 0a32e4f0025a74c70dcab4478e9b29c22f5ecf2f "btrfs: fix log tree replay
> failure due to file with 0 links and extents"
> 
> So just be sure to have that included, before you
> upgrad in unstable :-)

Actually the bug is older, but it is more likely to hit after
e85262e542d ("btrfs: fix fsync of files with no hard links not
persisting deletion") was backported.

See:
https://lore.kernel.org/linux-btrfs/fce139db-4458-4788-bb97-c29acf6cb1df@cachyos.org/
https://lore.kernel.org/linux-btrfs/lh4W-Lwc0Mbk-QvBhhQyZxf6VbM3E8VtIvU3fPIQgweP_Q1n7wtlUZQc33sYlCKYd-o6rryJQfhHaNAOWWRKxpAXhM8NZPojzsJPyHMf2qY=@protonmail.com/#t
https://lore.kernel.org/linux-btrfs/598ecc75-eb80-41b3-83c2-f2317fbb9864@gmail.com/

Regards,
Salvatore