[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: f6a2dae2a1f52ea23f649c02615d073beba4cc35
WARNING: Author mismatch between patch and upstream commit:
Backport author: Leah Rumancik<leah.rumancik@xxxxxxxxx>
Commit author: Darrick J. Wong<djwong@xxxxxxxxxx>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 0fbbfe5fbfbe)
6.1.y | Present (different SHA1: 5d1a85efae8f)
Note: The patch differs from the upstream commit:
---
1: f6a2dae2a1f52 ! 1: ce863045e9922 xfs: make sure maxlen is still congruent with prod when rounding down
@@ Metadata
## Commit message ##
xfs: make sure maxlen is still congruent with prod when rounding down
+ [ Upstream commit f6a2dae2a1f52ea23f649c02615d073beba4cc35 ]
+
In commit 2a6ca4baed62, we tried to fix an overflow problem in the
realtime allocator that was caused by an overly large maxlen value
causing xfs_rtcheck_range to run off the end of the realtime bitmap.
@@ Commit message
Fixes: 2a6ca4baed62 ("xfs: make sure the rt allocator doesn't run off the end")
Signed-off-by: Darrick J. Wong <djwong@xxxxxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
+ Signed-off-by: Leah Rumancik <leah.rumancik@xxxxxxxxx>
## fs/xfs/xfs_rtalloc.c ##
@@ fs/xfs/xfs_rtalloc.c: xfs_rtallocate_range(
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
