From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: AGF length has never been bounds checked
Date: Thu, 15 Jun 2023 21:19:01 -0700 [thread overview]
Message-ID: <20230616041901.GR11441@frogsfrogsfrogs> (raw)
In-Reply-To: <20230616015906.3813726-1-david@fromorbit.com>
On Fri, Jun 16, 2023 at 11:59:06AM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> The AGF verifier does not check that the AGF length field is within
> known good bounds. This has never been checked by runtime kernel
> code (i.e. the lack of verification goes back to 1993) yet we assume
Woo hoo!
> in many places that it is correct and verify other metdata against
> it.
>
> Add length verification to the AGF verifier. The length of the AGF
> must be equal to the size of the AG specified in the superblock,
> unless it is the last AG in the filesystem. In that case, it must be
> less than or equal to sb->sb_agblocks and greater than
> XFS_MIN_AG_BLOCKS, which is the smallest AG a growfs operation will
> allow to exist.
>
> This requires a bit of rework of the verifier function. We want to
> verify metadata before we use it to verify other metadata. Hence
> we need to verify the AGF sequence numbers before using them to
> verify the length of the AGF. Then we can verify the AGF length
> before we verify AGFL fields. Then we can verifier other fields that
> are bounds limited by the AGF length.
>
> And, finally, by calculating agf_length only once into a local
> variable, we can collapse repeated "if (xfs_has_foo() &&"
> conditionaly checks into single checks. This makes the code much
> easier to follow as all the checks for a given feature are obviously
> in the same place.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/libxfs/xfs_alloc.c | 81 ++++++++++++++++++++++-----------------
> 1 file changed, 46 insertions(+), 35 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
> index 7c675aae0a0f..78556cad57e5 100644
> --- a/fs/xfs/libxfs/xfs_alloc.c
> +++ b/fs/xfs/libxfs/xfs_alloc.c
> @@ -2970,6 +2970,7 @@ xfs_agf_verify(
> {
> struct xfs_mount *mp = bp->b_mount;
> struct xfs_agf *agf = bp->b_addr;
> + uint32_t agf_length = be32_to_cpu(agf->agf_length);
>
> if (xfs_has_crc(mp)) {
> if (!uuid_equal(&agf->agf_uuid, &mp->m_sb.sb_meta_uuid))
> @@ -2981,18 +2982,38 @@ xfs_agf_verify(
> if (!xfs_verify_magic(bp, agf->agf_magicnum))
> return __this_address;
>
> - if (!(XFS_AGF_GOOD_VERSION(be32_to_cpu(agf->agf_versionnum)) &&
> - be32_to_cpu(agf->agf_freeblks) <= be32_to_cpu(agf->agf_length) &&
> - be32_to_cpu(agf->agf_flfirst) < xfs_agfl_size(mp) &&
> - be32_to_cpu(agf->agf_fllast) < xfs_agfl_size(mp) &&
> - be32_to_cpu(agf->agf_flcount) <= xfs_agfl_size(mp)))
> + if (!(XFS_AGF_GOOD_VERSION(be32_to_cpu(agf->agf_versionnum))))
> return __this_address;
>
> - if (be32_to_cpu(agf->agf_length) > mp->m_sb.sb_dblocks)
> + /*
> + * during growfs operations, the perag is not fully initialised,
> + * so we can't use it for any useful checking. growfs ensures we can't
> + * use it by using uncached buffers that don't have the perag attached
> + * so we can detect and avoid this problem.
Would you mind adding an extra sentence here:
"Both agf_seqno and agf_length need to be validated before anything else
fsblock related in the AGF."
> + */
> + if (bp->b_pag && be32_to_cpu(agf->agf_seqno) != bp->b_pag->pag_agno)
> + return __this_address;
> +
> + /*
> + * Only the last AGF in the filesytsem is allowed to be shorter
> + * than the AG size recorded in the superblock.
> + */
> + if (agf_length != mp->m_sb.sb_agblocks) {
> + if (be32_to_cpu(agf->agf_seqno) != mp->m_sb.sb_agcount - 1)
> + return __this_address;
> + if (agf_length < XFS_MIN_AG_BLOCKS)
The superblock verifier checks that sb_agblocks >= XFS_MIN_AG_BYTES,
which means that it can't be less than 16MB. That's the lower bound on
the general AG size, not the lower bound of a runt AG at the end of the
fs.
OTOH, the lower bound of a runt AG is XFS_MIN_AG_BLOCKS, or 64FSB. I
would sorta like this to be outside this sub-block since that's
independent of whatever sb_agblocks is.
That said, there is no filesystem where setting sb_agblocks to 16MB
would result in an sb_agblocks with a value less than 256, so I suppose
this is a moot worry of mine.
Does that make sense?
> + return __this_address;
> + if (agf_length > mp->m_sb.sb_agblocks)
> + return __this_address;
> + }
> +
> + if (be32_to_cpu(agf->agf_flfirst) >= xfs_agfl_size(mp) ||
> + be32_to_cpu(agf->agf_fllast) >= xfs_agfl_size(mp) ||
> + be32_to_cpu(agf->agf_flcount) > xfs_agfl_size(mp))
> return __this_address;
I wish each check would get its own return __this_address. Today I was
debugging some dumb bug but addr2line dropped me off in the middle of
this mound of code. :(
Oh well, not required to land /this/ patch. Everything else in this
patch looks good.
--D
>
> if (be32_to_cpu(agf->agf_freeblks) < be32_to_cpu(agf->agf_longest) ||
> - be32_to_cpu(agf->agf_freeblks) > be32_to_cpu(agf->agf_length))
> + be32_to_cpu(agf->agf_freeblks) > agf_length)
> return __this_address;
>
> if (be32_to_cpu(agf->agf_levels[XFS_BTNUM_BNO]) < 1 ||
> @@ -3003,38 +3024,28 @@ xfs_agf_verify(
> mp->m_alloc_maxlevels)
> return __this_address;
>
> - if (xfs_has_rmapbt(mp) &&
> - (be32_to_cpu(agf->agf_levels[XFS_BTNUM_RMAP]) < 1 ||
> - be32_to_cpu(agf->agf_levels[XFS_BTNUM_RMAP]) >
> - mp->m_rmap_maxlevels))
> - return __this_address;
> -
> - if (xfs_has_rmapbt(mp) &&
> - be32_to_cpu(agf->agf_rmap_blocks) > be32_to_cpu(agf->agf_length))
> - return __this_address;
> -
> - /*
> - * during growfs operations, the perag is not fully initialised,
> - * so we can't use it for any useful checking. growfs ensures we can't
> - * use it by using uncached buffers that don't have the perag attached
> - * so we can detect and avoid this problem.
> - */
> - if (bp->b_pag && be32_to_cpu(agf->agf_seqno) != bp->b_pag->pag_agno)
> - return __this_address;
> -
> if (xfs_has_lazysbcount(mp) &&
> - be32_to_cpu(agf->agf_btreeblks) > be32_to_cpu(agf->agf_length))
> + be32_to_cpu(agf->agf_btreeblks) > agf_length)
> return __this_address;
>
> - if (xfs_has_reflink(mp) &&
> - be32_to_cpu(agf->agf_refcount_blocks) >
> - be32_to_cpu(agf->agf_length))
> - return __this_address;
> + if (xfs_has_rmapbt(mp)) {
> + if (be32_to_cpu(agf->agf_rmap_blocks) > agf_length)
> + return __this_address;
>
> - if (xfs_has_reflink(mp) &&
> - (be32_to_cpu(agf->agf_refcount_level) < 1 ||
> - be32_to_cpu(agf->agf_refcount_level) > mp->m_refc_maxlevels))
> - return __this_address;
> + if (be32_to_cpu(agf->agf_levels[XFS_BTNUM_RMAP]) < 1 ||
> + be32_to_cpu(agf->agf_levels[XFS_BTNUM_RMAP]) >
> + mp->m_rmap_maxlevels)
> + return __this_address;
> + }
> +
> + if (xfs_has_reflink(mp)) {
> + if (be32_to_cpu(agf->agf_refcount_blocks) > agf_length)
> + return __this_address;
> +
> + if (be32_to_cpu(agf->agf_refcount_level) < 1 ||
> + be32_to_cpu(agf->agf_refcount_level) > mp->m_refc_maxlevels)
> + return __this_address;
> + }
>
> return NULL;
> }
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-06-16 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 1:59 [PATCH] xfs: AGF length has never been bounds checked Dave Chinner
2023-06-16 4:19 ` Darrick J. Wong [this message]
2023-06-16 6:34 ` Dave Chinner
2023-06-16 7:41 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230616041901.GR11441@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox