From: Liu Bo <bo.li.liu@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 6/6] Btrfs: add sanity check of extent item in scrub
Date: Fri, 26 May 2017 13:20:14 -0700 [thread overview]
Message-ID: <20170526202014.GD7859@lim.localdomain> (raw)
In-Reply-To: <20170526183316.GN30842@twin.jikos.cz>
On Fri, May 26, 2017 at 08:33:16PM +0200, David Sterba wrote:
> On Thu, May 25, 2017 at 06:26:31PM -0600, Liu Bo wrote:
> > Currently scrub only verify checksum of both metadata and data and
> > couldn't detect an invalid extent_item.
>
> This is a different kind of check that scrub was never designed to do.
> Scrub just verifies the checksums, not the sructural integrity. This has
> been referred to as an "on-line fsck". AFAIK xfs does not use 'scrub' in
> the same sense as btrfs, so things are going to be confusing for the
> users.
>
> The on-line fsck is still desired, but I'd like to see a discussion how
> exactly it should work, whether to extend scrub or add a new ioctl etc.
>
I was hesitating about scrub vs online fsck when posting, just thought
it'd be good when users got this error while doing a regular scrub
ahead of really getting into trouble. If we have a plan for online
fsck, I'm happy to let fsck do the job.
Or we can do this kind of sanity check at the time when reading the
eb.
Thanks,
-liubo
> > This adds sanity check for extent item, now it can check if
> > extent_inline_ref_type is valid.
> >
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > fs/btrfs/scrub.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> >
> > diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c
> > index b0251eb..e87b752 100644
> > --- a/fs/btrfs/scrub.c
> > +++ b/fs/btrfs/scrub.c
> > @@ -3058,6 +3058,39 @@ static noinline_for_stack int scrub_raid56_parity(struct scrub_ctx *sctx,
> > return ret < 0 ? ret : 0;
> > }
> >
> > +static int check_extent_item(struct extent_buffer *l, int slot,
>
> Please use 'eb' for the extent_buffer.
>
> > + struct btrfs_extent_item *ei, int key_type)
>
> key_type should be u8
>
> > +{
> > + unsigned long ptr;
> > + unsigned long end;
> > + struct btrfs_extent_inline_ref *iref;
> > + u64 flags = btrfs_extent_flags(l, ei);
> > + int is_data = !!(flags & BTRFS_EXTENT_FLAG_DATA);
> > + int type;
> > +
> > + ptr = (unsigned long)(ei + 1);
> > + if (!is_data &&
> > + key_type != BTRFS_METADATA_ITEM_KEY)
> > + ptr += sizeof(struct btrfs_tree_block_info);
> > + end = (unsigned long)ei +
> > + btrfs_item_size_nr(l, slot);
>
> This will fit to one line
>
> > +
> > + while (1) {
> > + if (ptr >= end) {
> > + WARN_ON(ptr > end);
>
> Please add some verbose error message or get rid of the WARN_ON
> completely if possible.
>
> > + break;
> > + }
> > +
> > + iref = (struct btrfs_extent_inline_ref *)ptr;
> > + type = btrfs_get_extent_inline_ref_type(l, iref, is_data);
> > + if (type < 0)
> > + return type;
> > +
> > + ptr += btrfs_extent_inline_ref_size(type);
> > + }
> > + return 0;
> > +}
> > +
> > static noinline_for_stack int scrub_stripe(struct scrub_ctx *sctx,
> > struct map_lookup *map,
> > struct btrfs_device *scrub_dev,
> > @@ -3318,6 +3351,16 @@ static noinline_for_stack int scrub_stripe(struct scrub_ctx *sctx,
> > goto next;
> > }
> >
> > + /* sanity check for extent inline ref type */
> > + if (check_extent_item(l, slot, extent, key.type)) {
> > + btrfs_err(fs_info,
> > + "scrub: extent %llu(0x%llx) has an invalid extent inline ref type, ignored.",
>
> Strings can be un-indented to the left.
>
> > + key.objectid, key.objectid);
> > + spin_lock(&sctx->stat_lock);
> > + sctx->stat.uncorrectable_errors++;
>
> Yeah, this is an example where the uncorrectable_error would gain a new
> meaning. We'd need to extend the scrub error reporting so the various
> metadata errors get reported properly and not mangled with the rest.
>
> > + spin_unlock(&sctx->stat_lock);
> > + goto next;
> > + }
> > again:
> > extent_logical = key.objectid;
> > extent_len = bytes;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-26 20:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 0:26 [PATCH 0/6] add sanity check for extent inline ref type Liu Bo
2017-05-26 0:26 ` [PATCH 1/6] Btrfs: add a helper to retrive " Liu Bo
2017-05-26 7:09 ` Nikolay Borisov
2017-05-26 17:44 ` Jeff Mahoney
2017-05-26 18:13 ` David Sterba
2017-05-26 18:15 ` David Sterba
2017-05-26 0:26 ` [PATCH 2/6] Btrfs: convert to use btrfs_get_extent_inline_ref_type Liu Bo
2017-05-26 0:26 ` [PATCH 3/6] Btrfs: remove BUG() in btrfs_extent_inline_ref_size Liu Bo
2017-05-26 0:26 ` [PATCH 4/6] Btrfs: remove BUG() in print_extent_item Liu Bo
2017-05-26 18:18 ` David Sterba
2017-05-26 19:52 ` Liu Bo
2017-05-26 0:26 ` [PATCH 5/6] Btrfs: remove BUG() in add_data_reference Liu Bo
2017-05-26 18:20 ` David Sterba
2017-05-26 20:01 ` Liu Bo
2017-05-26 0:26 ` [PATCH 6/6] Btrfs: add sanity check of extent item in scrub Liu Bo
2017-05-26 18:33 ` David Sterba
2017-05-26 20:20 ` Liu Bo [this message]
2017-05-29 1:48 ` Qu Wenruo
2017-05-29 13:49 ` David Sterba
2017-05-30 14:05 ` [PATCH 0/6] add sanity check for extent inline ref type Ivan Sizov
2017-05-30 18:02 ` Liu Bo
2017-05-30 18:57 ` Ivan Sizov
2017-06-01 17:35 ` Liu Bo
2017-06-01 20:26 ` Ivan Sizov
2017-06-01 22:57 ` Liu Bo
2017-06-19 9:06 ` Ivan Sizov
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=20170526202014.GD7859@lim.localdomain \
--to=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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).