From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/7] xfs: check the ir_startino alignment directly
Date: Wed, 9 Jan 2019 08:32:26 -0500 [thread overview]
Message-ID: <20190109133226.GA13613@bfoster> (raw)
In-Reply-To: <154697956749.2494.10156686086778734160.stgit@magnolia>
On Tue, Jan 08, 2019 at 12:32:47PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> In xchk_iallocbt_rec, check the alignment of ir_startino by converting
> the inode cluster block alignment into units of inodes instead of the
> other way around (converting ir_startino to blocks). This prevents us
> from tripping over off-by-one errors in ir_startino which are obscured
> by the inode -> block conversion.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/scrub/ialloc.c | 56 ++++++++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 50 insertions(+), 6 deletions(-)
>
>
> diff --git a/fs/xfs/scrub/ialloc.c b/fs/xfs/scrub/ialloc.c
> index fd431682db0b..1c6fef9b3799 100644
> --- a/fs/xfs/scrub/ialloc.c
> +++ b/fs/xfs/scrub/ialloc.c
> @@ -265,6 +265,53 @@ xchk_iallocbt_check_freemask(
> return error;
> }
>
> +/*
> + * Make sure this inode btree record is aligned properly. Because a fs block
> + * contains multiple inodes, we check that the inobt record is aligned to the
> + * correct inode, not just the correct block on disk. This results in a finer
> + * grained corruption check.
> + */
> +STATIC void
> +xchk_iallocbt_rec_alignment(
> + struct xchk_btree *bs,
> + struct xfs_inobt_rec_incore *irec)
> +{
> + struct xfs_mount *mp = bs->sc->mp;
> +
> + /*
> + * finobt records have different positioning requirements than inobt
> + * records: each finobt record must have a corresponding inobt record.
> + * That is checked in the xref function, so for now we only catch the
> + * obvious case where the record isn't at all aligned properly.
> + *
> + * Note that if a fs block contains more than a single chunk of inodes,
> + * we will have finobt records only for those chunks containing free
> + * inodes, and therefore expect chunk alignment of finobt records.
> + * Otherwise, we expect that the finobt record is aligned to the
> + * cluster alignment as told by the superblock.
> + */
> + if (bs->cur->bc_btnum == XFS_BTNUM_FINO) {
> + unsigned int imask;
> +
> + imask = min_t(unsigned int, XFS_INODES_PER_CHUNK,
> + mp->m_cluster_align_inodes) - 1;
> + if (irec->ir_startino & imask)
> + xchk_btree_set_corrupt(bs->sc, bs->cur, 0);
> + return;
> + }
> +
Don't we also need this large FSB alignment fixup for inobt records, or
am I still confused? :/ I.e., if ->m_cluster_align_inodes is 128 and
irec is the second inobt record in a block..
Brian
> + /* inobt records must be aligned to cluster and inoalignmnt size. */
> + if (irec->ir_startino & (mp->m_cluster_align_inodes - 1)) {
> + xchk_btree_set_corrupt(bs->sc, bs->cur, 0);
> + return;
> + }
> +
> + if (irec->ir_startino & (mp->m_inodes_per_cluster - 1)) {
> + xchk_btree_set_corrupt(bs->sc, bs->cur, 0);
> + return;
> + }
> +}
> +
> /* Scrub an inobt/finobt record. */
> STATIC int
> xchk_iallocbt_rec(
> @@ -277,7 +324,6 @@ xchk_iallocbt_rec(
> uint64_t holes;
> xfs_agnumber_t agno = bs->cur->bc_private.a.agno;
> xfs_agino_t agino;
> - xfs_agblock_t agbno;
> xfs_extlen_t len;
> int holecount;
> int i;
> @@ -304,11 +350,9 @@ xchk_iallocbt_rec(
> goto out;
> }
>
> - /* Make sure this record is aligned to cluster and inoalignmnt size. */
> - agbno = XFS_AGINO_TO_AGBNO(mp, irec.ir_startino);
> - if ((agbno & (mp->m_cluster_align - 1)) ||
> - (agbno & (mp->m_blocks_per_cluster - 1)))
> - xchk_btree_set_corrupt(bs->sc, bs->cur, 0);
> + xchk_iallocbt_rec_alignment(bs, &irec);
> + if (bs->sc->sm->sm_flags & XFS_SCRUB_OFLAG_CORRUPT)
> + goto out;
>
> iabt->inodes += irec.ir_count;
>
>
next prev parent reply other threads:[~2019-01-09 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 20:32 [PATCH v2 0/7] xfs: inode scrubber fixes Darrick J. Wong
2019-01-08 20:32 ` [PATCH 1/7] xfs: never try to scrub more than 64 inodes per inobt record Darrick J. Wong
2019-01-08 20:32 ` [PATCH 2/7] xfs: check the ir_startino alignment directly Darrick J. Wong
2019-01-09 13:32 ` Brian Foster [this message]
2019-01-09 16:37 ` Darrick J. Wong
2019-01-09 16:48 ` Brian Foster
2019-01-08 20:32 ` [PATCH 3/7] xfs: check inobt record alignment on big block filesystems Darrick J. Wong
2019-01-08 20:33 ` [PATCH 4/7] xfs: hoist inode cluster checks out of loop Darrick J. Wong
2019-01-08 20:33 ` [PATCH 5/7] xfs: clean up the inode cluster checking in the inobt scrub Darrick J. Wong
2019-01-08 20:33 ` [PATCH 6/7] xfs: scrub big block inode btrees correctly Darrick J. Wong
2019-01-09 13:32 ` Brian Foster
2019-01-08 20:33 ` [PATCH 7/7] xfs: consolidate scrub dinode mapping code into a single function Darrick J. Wong
2019-01-09 13:33 ` Brian Foster
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=20190109133226.GA13613@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.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;
as well as URLs for NNTP newsgroup(s).