From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/6] xfs: xrep_findroot_block should reject root blocks with siblings
Date: Thu, 27 Sep 2018 16:20:23 -0700 [thread overview]
Message-ID: <20180927232023.GC20086@magnolia> (raw)
In-Reply-To: <20180813165635.GA64121@bfoster>
On Mon, Aug 13, 2018 at 12:56:36PM -0400, Brian Foster wrote:
> On Sat, Aug 11, 2018 at 08:35:09AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > In xrep_findroot_block, if we find a candidate root block with sibling
> > pointers or sibling blocks on the same tree level, we should not return
> > that block as a tree root because root blocks cannot have siblings.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/scrub/repair.c | 47 +++++++++++++++++++++++++++++++++++++++++------
> > 1 file changed, 41 insertions(+), 6 deletions(-)
> >
> >
> > diff --git a/fs/xfs/scrub/repair.c b/fs/xfs/scrub/repair.c
> > index 17cf48564390..42d8c798ce7d 100644
> > --- a/fs/xfs/scrub/repair.c
> > +++ b/fs/xfs/scrub/repair.c
> > @@ -690,6 +690,7 @@ xrep_findroot_block(
> > struct xfs_buf *bp;
> > struct xfs_btree_block *btblock;
> > xfs_daddr_t daddr;
> > + int block_level;
> > int error;
> >
> > daddr = XFS_AGB_TO_DADDR(mp, ri->sc->sa.agno, agbno);
> > @@ -727,17 +728,51 @@ xrep_findroot_block(
> > goto out;
> > bp->b_ops = fab->buf_ops;
> >
> > - /* Ignore this block if it's lower in the tree than we've seen. */
> > - if (fab->root != NULLAGBLOCK &&
> > - xfs_btree_get_level(btblock) < fab->height)
> > - goto out;
> > -
> > /* Make sure we pass the verifiers. */
> > bp->b_ops->verify_read(bp);
> > if (bp->b_error)
> > goto out;
> > +
> > + /* If we've recorded a root candidate... */
> > + block_level = xfs_btree_get_level(btblock);
> > + if (fab->root != NULLAGBLOCK) {
> > + /*
> > + * ...and this no-sibling root block candidate has the same
> > + * level as the recorded candidate, there's no way we're going
> > + * to accept any candidates at this tree level. Stash a root
> > + * block of zero because the height is still valid, but no
> > + * AG btree can root at agblock 0. Callers should verify the
> > + * root agbno with xfs_verify_agbno...
> > + */
> > + if (block_level + 1 == fab->height) {
> > + fab->root = 0;
> > + goto out;
> > + }
> > +
> > + /*
> > + * ...and this no-sibling root block is lower in the tree than
> > + * the recorded root block candidate, just ignore it. There's
> > + * still a strong chance that something is wrong with the btree
> > + * itself, but that's not what we're fixing right now.
> > + */
> > + if (block_level < fab->height)
> > + goto out;
> > + }
> > +
> > + /*
> > + * Root blocks can't have siblings. This level can't be the root, so
> > + * record the tree height (but not the ag block pointer) to force us to
> > + * look for a higher level in the tree.
> > + */
> > + if (btblock->bb_u.s.bb_leftsib != cpu_to_be32(NULLAGBLOCK) ||
> > + btblock->bb_u.s.bb_rightsib != cpu_to_be32(NULLAGBLOCK)) {
> > + fab->root = 0;
> > + fab->height = block_level + 1;
> > + goto out;
> > + }
> > +
[Finally getting to this after weeks...]
> Hmm, this looks technically correct but this still seems more involved
> than necessary. I don't really like how we define yet another magic
> value of 0, for example, and differentiate that from NULLAGBLOCK when it
> seems like we could just check the height.
>
> Could we do something like the following (which assumes ->height is
> initialized to 0)?
Yes, ->height is initialized to zero.
> /*
> * If current height exceeds the block level, we've already seen at
> * least one block at this level or higher. Skip it and invalidate the
> * root if this block matches the current root level because a root
> * block has no siblings.
> */
> block_level = xfs_btree_get_level(btblock);
> if (fab->height > block_level) {
> if (fab->height - 1 == block_level)
> fab->root = NULLAGBLOCK;
> goto out;
> }
Yes, I think that will work. I might be a little more explicit that
we're handling two cases here.
> /*
> * Found a block with a new max height. Track it as a root candidate if
> * it has no siblings. Otherwise invalidate root since we know the root
> * can't be at this level.
> */
> if (btblock->bb_u.s.bb_leftsib == cpu_to_be32(NULLAGBLOCK) &&
> btblock->bb_u.s.bb_rightsib == cpu_to_be32(NULLAGBLOCK))
> fab->root = agbno;
> else
> fab->root = NULLAGBLOCK;
> fab->height = block_level + 1;
>
> ... and then ->root should either be valid or NULLAGBLOCK at the end..?
Correct. This is much better. :)
> Also, shouldn't we set *found_it a bit earlier in this function? It
> looks like that simply controls the fab iteration and we have
> technically matched the block to a btree type at this point, regardless
> of whether we update root/height. (I wonder if something like "matched"
> or "found_match" might be a better name than found_it...).
If the block passes the magic number/uuid/verifier tests then we're
certain that the block belongs to this btree type and we don't need to
try the other btree types. Therefore, *found_it should indeed be set
earlier in the function. It should probably be renamed *done or
something.
Ok so here's the new code, starting right after we finish the
magic/uuid/verifier tests:
/*
* This block passes the magic number and verifier test for this tree
* type. We don't need the caller to try the other tree types.
*/
*done_with_block = true;
block_level = xfs_btree_get_level(btblock);
if (block_level + 1 == fab->height) {
/*
* This block claims to be at the same level as the root we
* found previously. There can't be two candidate roots, so
* we'll throw away both of them and hope we later find a block
* even higher in the tree.
*/
fab->root = NULLAGBLOCK;
goto out;
} else if (block_level < fab->height) {
/*
* This block is lower in the tree than the root we found
* previously, so just ignore it.
*/
goto out;
}
/*
* This is the highest block in the tree that we've found so far.
* Update the btree height to reflect what we've learned from this
* block.
*/
fab->height = block_level + 1;
/*
* If this block doesn't have sibling pointers, then it's the new root
* block candidate. Otherwise, the root will be found farther up the
* tree.
*/
if (btblock->bb_u.s.bb_leftsib == cpu_to_be32(NULLAGBLOCK) &&
btblock->bb_u.s.bb_rightsib == cpu_to_be32(NULLAGBLOCK))
fab->root = agbno;
else
fab->root = NULLAGBLOCK;
Will ship this out for testing and see what happens. :)
--D
>
> Brian
>
> > fab->root = agbno;
> > - fab->height = xfs_btree_get_level(btblock) + 1;
> > + fab->height = block_level + 1;
> > *found_it = true;
> >
> > trace_xrep_findroot_block(mp, ri->sc->sa.agno, agbno,
> >
next prev parent reply other threads:[~2018-09-28 5:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 15:34 [PATCH v2 0/6] xfs-4.19: various fixes Darrick J. Wong
2018-08-11 15:35 ` [PATCH 1/6] xfs: recalculate summary counters at mount time if icount is bad Darrick J. Wong
2018-08-12 7:53 ` Allison Henderson
2018-08-13 7:46 ` Carlos Maiolino
2018-08-11 15:35 ` [PATCH 2/6] xfs: xrep_findroot_block should reject root blocks with siblings Darrick J. Wong
2018-08-12 7:53 ` Allison Henderson
2018-08-13 7:48 ` Carlos Maiolino
2018-08-13 16:56 ` Brian Foster
2018-09-27 23:20 ` Darrick J. Wong [this message]
2018-08-11 15:35 ` [PATCH 3/6] xfs: sanity check ag header values in xrep_calc_ag_resblks Darrick J. Wong
2018-08-12 7:55 ` Allison Henderson
2018-08-13 7:52 ` Carlos Maiolino
2018-08-11 15:35 ` [PATCH 4/6] xfs: fix buffer state management in xrep_findroot_block Darrick J. Wong
2018-08-12 7:53 ` Allison Henderson
2018-08-13 8:05 ` Carlos Maiolino
2018-08-13 16:56 ` Brian Foster
2018-09-28 0:32 ` Darrick J. Wong
2018-08-13 22:56 ` Dave Chinner
2018-09-28 0:28 ` Darrick J. Wong
2018-08-11 15:35 ` [PATCH 5/6] iomap: fix WARN_ON_ONCE on uninitialized variable Darrick J. Wong
2018-08-12 7:55 ` Allison Henderson
2018-08-13 8:07 ` Carlos Maiolino
2018-08-11 15:35 ` [PATCH 6/6] xfs: don't crash the vfs on a garbage inline symlink Darrick J. Wong
2018-08-12 7:54 ` Allison Henderson
2018-08-13 7:23 ` Christoph Hellwig
2018-09-28 0:31 ` Darrick J. Wong
2018-08-19 21:07 ` Xu, Wen
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=20180927232023.GC20086@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.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).