[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected. No action required from the submitter.
The upstream commit SHA1 provided is correct: 968f19c5b1b7d5595423b0ac0020cc18dfed8cb5
Status in newer kernel trees: 6.14.y | Not found
Note: The patch differs from the upstream commit: --- 1: 968f19c5b1b7d ! 1: 9ab4b4f9bed11 btrfs: always fallback to buffered write if the inode requires checksum @@ Metadata ## Commit message ## btrfs: always fallback to buffered write if the inode requires checksum
+ commit 968f19c5b1b7d5595423b0ac0020cc18dfed8cb5 upstream. + [BUG] It is a long known bug that VM image on btrfs can lead to data csum mismatch, if the qemu is using direct-io for the image (this is commonly @@ Commit message filesystems have no extra checksum on data, the content change is not a problem at all.
- But the final write into the image file is handled by btrfs, which needs + Bu the final write into the image file is handled by btrfs, which needs the content not to be modified during writeback, or the checksum will not match the data (checksum is calculated before submitting the bio).
@@ Commit message to buffered IO. At least by this, we avoid the more deadly false data checksum mismatch error.
+ CC: stable@vger.kernel.org # 6.12+ Suggested-by: Christoph Hellwig hch@infradead.org Reviewed-by: Filipe Manana fdmanana@suse.com Signed-off-by: Qu Wenruo wqu@suse.com ---
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-6.12.y | Success | Success |