Bug#1017915: btrfs: space cache corruption and potential double allocations
Source: linux
Version: 5.18.16-1
Severity: important
Tags: upstream patch
Hey.
This is merely a heads up, that a potentially pretty nasty data corruption
issue has been found in btrfs.
As far as I understand:
It was introduced in 5.12, has the highest chances to occur with
free space cache v2, but may also happen with v1 or even nospace_cache.
v2 was made default with btrfs-progs 5.15.
It seems that it may in principle affect data and metadata, so could range from
single file corruptions to complete fs breakage?
The patch, which AFAICS hasn't been submitted to linux-stable yet, can be found
here:
https://lore.kernel.org/linux-btrfs/cover.1660690698.git.osandov@fb.com/
A more in-depth description can be found in it's first commit.
Some others and I myself have asked some further questions about the issue
(how one can detect any corruptions, and so on), which can also be found
in the very same mail thread.
Not sure if the above patch is already production read, but at least it would
be quite helpful if it could be cherry-picked for testing/sid as soon as it has
landed in linux-stable.
Thanks,
Chris.
Reply to: