From: Darrick J. Wong Date: Mon, 25 Nov 2024 21:14:26 +0000 (-0800) Subject: xfs: adjust min_block usage in xfs_verify_agbno X-Git-Tag: v6.13.0~97 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6713ab810c4edf5daa8367b949c91c4ef605b0d9;p=thirdparty%2Fxfsprogs-dev.git xfs: adjust min_block usage in xfs_verify_agbno Source kernel commit: ceaa0bd773e2d6d5726d6535f605ecd6b26d2fcc There's some weird logic in xfs_verify_agbno -- min_block ought to be the first agblock number in the AG that can be used by non-static metadata. However, we initialize it to the last agblock of the static metadata, which works due to the <= check, even though this isn't technically correct. Change the check to < and set min_block to the next agblock past the static metadata. This hasn't been an issue up to now, but we're going to move these things into the generic group struct, and this will cause problems with rtgroups, where min_block can be zero for an rtgroup that doesn't have a rt superblock. Note that there's no user-visible impact with the old logic, so this isn't a bug fix. Signed-off-by: Darrick J. Wong Reviewed-by: Christoph Hellwig --- diff --git a/libxfs/xfs_ag.c b/libxfs/xfs_ag.c index bd38ac17..181e9291 100644 --- a/libxfs/xfs_ag.c +++ b/libxfs/xfs_ag.c @@ -240,7 +240,7 @@ xfs_perag_alloc( * Pre-calculated geometry */ pag->block_count = __xfs_ag_block_count(mp, index, agcount, dblocks); - pag->min_block = XFS_AGFL_BLOCK(mp); + pag->min_block = XFS_AGFL_BLOCK(mp) + 1; __xfs_agino_range(mp, pag->block_count, &pag->agino_min, &pag->agino_max); diff --git a/libxfs/xfs_ag.h b/libxfs/xfs_ag.h index 7290148f..9c22a76d 100644 --- a/libxfs/xfs_ag.h +++ b/libxfs/xfs_ag.h @@ -222,7 +222,7 @@ xfs_verify_agbno(struct xfs_perag *pag, xfs_agblock_t agbno) { if (agbno >= pag->block_count) return false; - if (agbno <= pag->min_block) + if (agbno < pag->min_block) return false; return true; }