From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 01/10] xfs: hoist recovered bmap intent checks out of xfs_bui_item_recover
Date: Fri, 4 Dec 2020 08:55:06 -0500 [thread overview]
Message-ID: <20201204135506.GC1404170@bfoster> (raw)
In-Reply-To: <160704430044.734470.16065444609448176719.stgit@magnolia>
On Thu, Dec 03, 2020 at 05:11:40PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> When we recover a bmap intent from the log, we need to validate its
> contents before we try to replay them. Hoist the checking code into a
> separate function in preparation to refactor this code to use validation
> helpers.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/xfs_bmap_item.c | 73 ++++++++++++++++++++++++++++++------------------
> 1 file changed, 46 insertions(+), 27 deletions(-)
>
>
> diff --git a/fs/xfs/xfs_bmap_item.c b/fs/xfs/xfs_bmap_item.c
> index 9e16a4d0f97c..555453d0e080 100644
> --- a/fs/xfs/xfs_bmap_item.c
> +++ b/fs/xfs/xfs_bmap_item.c
> @@ -417,6 +417,49 @@ const struct xfs_defer_op_type xfs_bmap_update_defer_type = {
> .cancel_item = xfs_bmap_update_cancel_item,
> };
>
> +/* Is this recovered BUI ok? */
> +static inline bool
> +xfs_bui_validate(
> + struct xfs_mount *mp,
> + struct xfs_bui_log_item *buip)
> +{
> + struct xfs_map_extent *bmap;
> + xfs_fsblock_t startblock_fsb;
> + xfs_fsblock_t inode_fsb;
> +
> + /* Only one mapping operation per BUI... */
> + if (buip->bui_format.bui_nextents != XFS_BUI_MAX_FAST_EXTENTS)
> + return false;
> +
> + bmap = &buip->bui_format.bui_extents[0];
> + startblock_fsb = XFS_BB_TO_FSB(mp,
> + XFS_FSB_TO_DADDR(mp, bmap->me_startblock));
> + inode_fsb = XFS_BB_TO_FSB(mp, XFS_FSB_TO_DADDR(mp,
> + XFS_INO_TO_FSB(mp, bmap->me_owner)));
> +
> + if (bmap->me_flags & ~XFS_BMAP_EXTENT_FLAGS)
> + return false;
> +
> + switch (bmap->me_flags & XFS_BMAP_EXTENT_TYPE_MASK) {
> + case XFS_BMAP_MAP:
> + case XFS_BMAP_UNMAP:
> + break;
> + default:
> + return false;
> + }
> +
> + if (startblock_fsb == 0 ||
> + bmap->me_len == 0 ||
> + inode_fsb == 0 ||
> + startblock_fsb >= mp->m_sb.sb_dblocks ||
> + bmap->me_len >= mp->m_sb.sb_agblocks ||
> + inode_fsb >= mp->m_sb.sb_dblocks ||
> + (bmap->me_flags & ~XFS_BMAP_EXTENT_FLAGS))
> + return false;
Looks like the ->me_flags check is duplicated here and above. Otherwise
looks good:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> +
> + return true;
> +}
> +
> /*
> * Process a bmap update intent item that was recovered from the log.
> * We need to update some inode's bmbt.
> @@ -433,47 +476,23 @@ xfs_bui_item_recover(
> struct xfs_mount *mp = lip->li_mountp;
> struct xfs_map_extent *bmap;
> struct xfs_bud_log_item *budp;
> - xfs_fsblock_t startblock_fsb;
> - xfs_fsblock_t inode_fsb;
> xfs_filblks_t count;
> xfs_exntst_t state;
> unsigned int bui_type;
> int whichfork;
> int error = 0;
>
> - /* Only one mapping operation per BUI... */
> - if (buip->bui_format.bui_nextents != XFS_BUI_MAX_FAST_EXTENTS)
> + if (!xfs_bui_validate(mp, buip)) {
> + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, mp);
> return -EFSCORRUPTED;
> + }
>
> - /*
> - * First check the validity of the extent described by the
> - * BUI. If anything is bad, then toss the BUI.
> - */
> bmap = &buip->bui_format.bui_extents[0];
> - startblock_fsb = XFS_BB_TO_FSB(mp,
> - XFS_FSB_TO_DADDR(mp, bmap->me_startblock));
> - inode_fsb = XFS_BB_TO_FSB(mp, XFS_FSB_TO_DADDR(mp,
> - XFS_INO_TO_FSB(mp, bmap->me_owner)));
> state = (bmap->me_flags & XFS_BMAP_EXTENT_UNWRITTEN) ?
> XFS_EXT_UNWRITTEN : XFS_EXT_NORM;
> whichfork = (bmap->me_flags & XFS_BMAP_EXTENT_ATTR_FORK) ?
> XFS_ATTR_FORK : XFS_DATA_FORK;
> bui_type = bmap->me_flags & XFS_BMAP_EXTENT_TYPE_MASK;
> - switch (bui_type) {
> - case XFS_BMAP_MAP:
> - case XFS_BMAP_UNMAP:
> - break;
> - default:
> - return -EFSCORRUPTED;
> - }
> - if (startblock_fsb == 0 ||
> - bmap->me_len == 0 ||
> - inode_fsb == 0 ||
> - startblock_fsb >= mp->m_sb.sb_dblocks ||
> - bmap->me_len >= mp->m_sb.sb_agblocks ||
> - inode_fsb >= mp->m_sb.sb_dblocks ||
> - (bmap->me_flags & ~XFS_BMAP_EXTENT_FLAGS))
> - return -EFSCORRUPTED;
>
> /* Grab the inode. */
> error = xfs_iget(mp, NULL, bmap->me_owner, 0, 0, &ip);
>
next prev parent reply other threads:[~2020-12-04 13:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 1:11 [PATCH v2 00/10] xfs: strengthen log intent validation Darrick J. Wong
2020-12-04 1:11 ` [PATCH 01/10] xfs: hoist recovered bmap intent checks out of xfs_bui_item_recover Darrick J. Wong
2020-12-04 13:55 ` Brian Foster [this message]
2020-12-04 1:11 ` [PATCH 02/10] xfs: improve the code that checks recovered bmap intent items Darrick J. Wong
2020-12-04 13:56 ` Brian Foster
2020-12-04 19:54 ` Darrick J. Wong
2020-12-04 1:11 ` [PATCH 03/10] xfs: hoist recovered rmap intent checks out of xfs_rui_item_recover Darrick J. Wong
2020-12-04 13:59 ` Brian Foster
2020-12-04 1:12 ` [PATCH 04/10] xfs: improve the code that checks recovered rmap intent items Darrick J. Wong
2020-12-04 13:59 ` Brian Foster
2020-12-04 1:12 ` [PATCH 05/10] xfs: hoist recovered refcount intent checks out of xfs_cui_item_recover Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-04 1:12 ` [PATCH 06/10] xfs: improve the code that checks recovered refcount intent items Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-04 1:12 ` [PATCH 07/10] xfs: hoist recovered extent-free intent checks out of xfs_efi_item_recover Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-04 1:12 ` [PATCH 08/10] xfs: improve the code that checks recovered extent-free intent items Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-04 1:12 ` [PATCH 09/10] xfs: validate feature support when recovering rmap/refcount/bmap intents Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-06 23:08 ` Darrick J. Wong
2020-12-07 14:02 ` Brian Foster
2020-12-07 16:50 ` Darrick J. Wong
2020-12-04 1:12 ` [PATCH 10/10] xfs: trace log intent item recovery failures Darrick J. Wong
2020-12-04 14:00 ` Brian Foster
2020-12-04 19:57 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2020-12-06 23:09 [PATCH v3 00/10] xfs: strengthen log intent validation Darrick J. Wong
2020-12-06 23:09 ` [PATCH 01/10] xfs: hoist recovered bmap intent checks out of xfs_bui_item_recover Darrick J. Wong
2020-12-01 3:37 [PATCH 00/10] xfs: strengthen log intent validation Darrick J. Wong
2020-12-01 3:37 ` [PATCH 01/10] xfs: hoist recovered bmap intent checks out of xfs_bui_item_recover Darrick J. Wong
2020-12-01 10:02 ` 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=20201204135506.GC1404170@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).