From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: david@fromorbit.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] xfs: fix buffer state management in xrep_findroot_block
Date: Tue, 9 Oct 2018 09:19:55 -0700 [thread overview]
Message-ID: <20181009161955.GH28243@magnolia> (raw)
In-Reply-To: <20181009121638.GB2816@bfoster>
On Tue, Oct 09, 2018 at 08:16:39AM -0400, Brian Foster wrote:
> On Mon, Oct 08, 2018 at 09:19:47PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > We don't handle buffer state properly in online repair's findroot
> > routine. If a buffer already has b_ops set, we don't ever want to touch
> > that, and we don't want to call the read verifiers on a buffer that
> > could be dirty (CRCs are only recomputed during log checkpoints).
> >
> > Therefore, be more careful about what we do with a buffer -- if someone
> > else already attached ops that are not the ones for this btree type,
> > just ignore the buffer. We only attach our btree type's buf ops if it
> > matches the magic/uuid and structure checks.
> >
> > We also modify xfs_buf_read_map to allow callers to set buffer ops on a
> > DONE buffer with NULL ops so that repair doesn't leave behind buffers
> > which won't have buffers attached to them.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/scrub/repair.c | 65 ++++++++++++++++++++++++++++++++++++++----------
> > fs/xfs/xfs_trans.h | 1 +
> > fs/xfs/xfs_trans_buf.c | 13 ++++++++++
> > 3 files changed, 65 insertions(+), 14 deletions(-)
> >
> >
> > diff --git a/fs/xfs/scrub/repair.c b/fs/xfs/scrub/repair.c
> > index 63786341ac2a..a07b9364c9de 100644
> > --- a/fs/xfs/scrub/repair.c
> > +++ b/fs/xfs/scrub/repair.c
> > @@ -29,6 +29,8 @@
> > #include "xfs_ag_resv.h"
> > #include "xfs_trans_space.h"
> > #include "xfs_quota.h"
> > +#include "xfs_attr.h"
> > +#include "xfs_reflink.h"
> > #include "scrub/xfs_scrub.h"
> > #include "scrub/scrub.h"
> > #include "scrub/common.h"
> > @@ -699,7 +701,7 @@ xrep_findroot_block(
> > struct xfs_btree_block *btblock;
> > xfs_daddr_t daddr;
> > int block_level;
> > - int error;
> > + int error = 0;
> >
> > daddr = XFS_AGB_TO_DADDR(mp, ri->sc->sa.agno, agbno);
> >
> > @@ -718,28 +720,63 @@ xrep_findroot_block(
> > return error;
> > }
> >
> > + /*
> > + * Read the buffer into memory so that we can see if it's a match for
> > + * our btree type. We have no clue if it is beforehand, and we want to
> > + * avoid xfs_trans_read_buf's behavior of dumping the DONE state (which
> > + * will cause needless disk reads in subsequent calls to this function)
> > + * and logging metadata verifier failures.
> > + *
> > + * Therefore, pass in NULL buffer ops. If the buffer was already in
> > + * memory from some other caller it will already have b_ops assigned.
> > + * If it was in memory from a previous unsuccessful findroot_block
> > + * call, the buffer won't have b_ops but it should be clean and ready
> > + * for us to try to verify if the read call succeeds. The same applies
> > + * if the buffer wasn't in memory at all.
> > + *
> > + * Note: If we never match a btree type with this buffer, it will be
> > + * left in memory with NULL b_ops. This shouldn't be a problem unless
> > + * the buffer gets written.
> > + */
> > error = xfs_trans_read_buf(mp, ri->sc->tp, mp->m_ddev_targp, daddr,
> > mp->m_bsize, 0, &bp, NULL);
> > if (error)
> > return error;
> >
> > - /*
> > - * Does this look like a block matching our fs and higher than any
> > - * other block we've found so far? If so, reattach buffer verifiers
> > - * so the AIL won't complain if the buffer is also dirty.
> > - */
> > + /* Ensure the block magic matches the btree type we're looking for. */
> > btblock = XFS_BUF_TO_BLOCK(bp);
> > if (be32_to_cpu(btblock->bb_magic) != fab->magic)
> > goto out;
> > - if (xfs_sb_version_hascrc(&mp->m_sb) &&
> > - !uuid_equal(&btblock->bb_u.s.bb_uuid, &mp->m_sb.sb_meta_uuid))
> > - goto out;
> > - bp->b_ops = fab->buf_ops;
> >
> > - /* Make sure we pass the verifiers. */
> > - bp->b_ops->verify_read(bp);
> > - if (bp->b_error)
> > - goto out;
> > + /*
> > + * If the buffer already has ops applied and they're not the ones for
> > + * this btree type, we know this block doesn't match the btree and we
> > + * can bail out.
> > + *
> > + * If the buffer ops match ours, someone else has already validated
> > + * the block for us, so we can move on to checking if this is a root
> > + * block candidate.
> > + *
> > + * If the buffer does not have ops, nobody has successfully validated
> > + * the contents and the buffer cannot be dirty. If the magic, uuid,
> > + * and structure match this btree type then we'll move on to checking
> > + * if it's a root block candidate. If there is no match, bail out.
> > + */
> > + if (bp->b_ops) {
> > + if (bp->b_ops != fab->buf_ops)
> > + goto out;
> > + } else {
> > + ASSERT(!xfs_trans_buf_is_dirty(bp));
> > + if (!uuid_equal(&btblock->bb_u.s.bb_uuid,
> > + &mp->m_sb.sb_meta_uuid))
> > + goto out;
> > + fab->buf_ops->verify_read(bp);
> > + if (bp->b_error) {
> > + bp->b_error = 0;
> > + goto out;
> > + }
> > + bp->b_ops = fab->buf_ops;
>
> In light of the assert issues you hit on the previous patch related to
> verifiers reassigning ->b_ops, perhaps we should think about clearing
> ->b_ops on error and making the line above something like:
>
> if (!bp->b_ops)
> bp->b_ops = fab->buf_ops;
>
> I guess this mechanism is only for per-ag btrees atm, but that could be
> a fun landmine to deal with if this rmap searching/detecting code is
> ever repurposed to deal with directories/attrs or other verifiers are
> updated to do a similar kind of reassignment. Not an immediate issue
> (and I don't want to nit this patch to death :P), so:
This function was only ever meant to find AG btree roots (and the
dir/attr code uses a different strategy to recover its marbles), but
there's still time to revise the patch to avoid that landmine, so I'll
go ahead and add that in:
/*
* Some read verifiers will (re)set b_ops, so we must be
* careful not to blow away any such assignment.
*/
if (!bp->b_ops)
bp->b_ops = fab->buf_ops;
Thanks for the review!
--D
> Reviewed-by: Brian Foster <bfoster@redhat.com>
>
> > + }
> >
> > /*
> > * This block passes the magic/uuid and verifier tests for this btree
> > diff --git a/fs/xfs/xfs_trans.h b/fs/xfs/xfs_trans.h
> > index c3d278e96ad1..a0c5dbda18aa 100644
> > --- a/fs/xfs/xfs_trans.h
> > +++ b/fs/xfs/xfs_trans.h
> > @@ -220,6 +220,7 @@ void xfs_trans_ijoin(struct xfs_trans *, struct xfs_inode *, uint);
> > void xfs_trans_log_buf(struct xfs_trans *, struct xfs_buf *, uint,
> > uint);
> > void xfs_trans_dirty_buf(struct xfs_trans *, struct xfs_buf *);
> > +bool xfs_trans_buf_is_dirty(struct xfs_buf *bp);
> > void xfs_trans_log_inode(xfs_trans_t *, struct xfs_inode *, uint);
> >
> > void xfs_extent_free_init_defer_op(void);
> > diff --git a/fs/xfs/xfs_trans_buf.c b/fs/xfs/xfs_trans_buf.c
> > index fc40160c1773..629f1479c9d2 100644
> > --- a/fs/xfs/xfs_trans_buf.c
> > +++ b/fs/xfs/xfs_trans_buf.c
> > @@ -350,6 +350,19 @@ xfs_trans_read_buf_map(
> >
> > }
> >
> > +/* Has this buffer been dirtied by anyone? */
> > +bool
> > +xfs_trans_buf_is_dirty(
> > + struct xfs_buf *bp)
> > +{
> > + struct xfs_buf_log_item *bip = bp->b_log_item;
> > +
> > + if (!bip)
> > + return false;
> > + ASSERT(bip->bli_item.li_type == XFS_LI_BUF);
> > + return test_bit(XFS_LI_DIRTY, &bip->bli_item.li_flags);
> > +}
> > +
> > /*
> > * Release a buffer previously joined to the transaction. If the buffer is
> > * modified within this transaction, decrement the recursion count but do not
> >
next prev parent reply other threads:[~2018-10-09 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 4:19 [PATCH v4 0/3] xfs-4.20: scrub fixes Darrick J. Wong
2018-10-09 4:19 ` [PATCH 1/3] xfs: xrep_findroot_block should reject root blocks with siblings Darrick J. Wong
2018-10-09 4:19 ` [PATCH 2/3] xfs: always assign buffer verifiers when one is provided Darrick J. Wong
2018-10-09 4:19 ` [PATCH 3/3] xfs: fix buffer state management in xrep_findroot_block Darrick J. Wong
2018-10-09 12:16 ` Brian Foster
2018-10-09 16:19 ` Darrick J. Wong [this message]
2018-10-09 18:46 ` [PATCH v2 " Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2018-10-05 0:47 [PATCH v3 0/3] xfs-4.20: scrub fixes Darrick J. Wong
2018-10-05 0:47 ` [PATCH 3/3] xfs: fix buffer state management in xrep_findroot_block Darrick J. Wong
2018-10-05 11:59 ` Brian Foster
2018-10-05 15:11 ` Darrick J. Wong
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=20181009161955.GH28243@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).