]> git.ipfire.org Git - thirdparty/xfsprogs-dev.git/commitdiff
xfs: adjust min_block usage in xfs_verify_agbno
authorDarrick J. Wong <djwong@kernel.org>
Mon, 25 Nov 2024 21:14:26 +0000 (13:14 -0800)
committerDarrick J. Wong <djwong@kernel.org>
Tue, 24 Dec 2024 02:01:31 +0000 (18:01 -0800)
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 <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
libxfs/xfs_ag.c
libxfs/xfs_ag.h

index bd38ac175bbae3da84af8ec541fc9bdc05827d41..181e929132d855acaa6c5c1203a6f3dfc54a4133 100644 (file)
@@ -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);
 
index 7290148fa6e6aaeefe01d344b6950f841b4d8505..9c22a76d58cfc2f730340734facf045cce0e85ed 100644 (file)
@@ -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;
 }