[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: d3b689d7c711a9f36d3e48db9eaa75784a892f4c
WARNING: Author mismatch between patch and upstream commit:
Backport author: Catherine Hoang <catherine.hoang@xxxxxxxxxx>
Commit author: John Garry <john.g.garry@xxxxxxxxxx>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: d3b689d7c711 ! 1: d90eb08021a2 xfs: Fix xfs_flush_unmap_range() range for RT
@@ Metadata
## Commit message ##
xfs: Fix xfs_flush_unmap_range() range for RT
+ commit d3b689d7c711a9f36d3e48db9eaa75784a892f4c upstream.
+
Currently xfs_flush_unmap_range() does unmap for a full RT extent range,
which we also want to ensure is clean and idle.
@@ Commit message
Reviewed-by: Darrick J. Wong <djwong@xxxxxxxxxx>
Signed-off-by: John Garry <john.g.garry@xxxxxxxxxx>
Signed-off-by: Chandan Babu R <chandanbabu@xxxxxxxxxx>
+ Signed-off-by: Catherine Hoang <catherine.hoang@xxxxxxxxxx>
+ Acked-by: Darrick J. Wong <djwong@xxxxxxxxxx>
## fs/xfs/xfs_bmap_util.c ##
@@ fs/xfs/xfs_bmap_util.c: xfs_flush_unmap_range(
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
