xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

Overview

In the Linux kernel, the following vulnerability has been resolved:

xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged.

That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files.

Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

Affected

• Linux >= 966ceafc7a437105ecfe1cadb3747b2965a260ca < 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66
• Linux >= 966ceafc7a437105ecfe1cadb3747b2965a260ca < 0f27b22343b63e10773e6781344640c2c753eec3
• Linux >= 966ceafc7a437105ecfe1cadb3747b2965a260ca < 03c9c9116e6da641424681f705698d7f5e2128e0
• Linux >= 966ceafc7a437105ecfe1cadb3747b2965a260ca < b2d5a81dae385333f9734910277fbf94c78bd17f
• Linux 6.10

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.