From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] Enhancement for block group/chunk verification
Date: Wed, 4 Jul 2018 15:36:07 +0200 [thread overview]
Message-ID: <20180704133607.GQ3126@twin.jikos.cz> (raw)
In-Reply-To: <20180703091009.16399-1-wqu@suse.com>
On Tue, Jul 03, 2018 at 05:10:04PM +0800, Qu Wenruo wrote:
> Can be fetched from github, which is based on v4.18-rc1 tag:
> https://github.com/adam900710/linux/tree/tree_checker_enhance
>
> Reported by Xu Wen <wen.xu@gatech.edu>, some crafted btrfs image can
> cause unexpected kernel behavior.
>
> All of them are related to block group and chunk, so this patchset will
> enhance block group and chunk verification, so kernel can detect them
> and error out gracefully (with user friendly error message showing
> what's going wrong)
>
> Obvious corruption (don't need to cross check with chunk/block group),
> will be addressed by enhanced tree-checker.
> (Most crafted images will be caught by tree-checker)
>
> More complex corruption will be addressed mostly at
> btrfs_read_block_groups(), doing extra cross reference check for
> chunk<->block group mapping.
> It may cause extra mount time, but compared to the existing time
> consuming block group items search, all added check is done completely
> in memory using rb_tree, so it shouldn't add too much overhead.
>
> Qu Wenruo (5):
> btrfs: tree-checker: Verify block_group_item
> btrfs: tree-checker: Detect invalid empty essential tree
> btrfs: relocation: Only remove reloc rb_trees if reloc control has
> been initialized
> btrfs: Check each block group has corresponding chunk at mount time
> btrfs: Verify every chunk has corresponding block group at mount time
Patches 1-3 queued, thanks. 4 and 5 have some comments.
next prev parent reply other threads:[~2018-07-04 13:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 9:10 [PATCH 0/5] Enhancement for block group/chunk verification Qu Wenruo
2018-07-03 9:10 ` [PATCH 1/5] btrfs: tree-checker: Verify block_group_item Qu Wenruo
2018-07-04 2:20 ` Gu, Jinxiang
2018-07-04 5:54 ` Nikolay Borisov
2018-07-04 7:37 ` Gu, Jinxiang
2018-07-03 9:10 ` [PATCH 2/5] btrfs: tree-checker: Detect invalid empty essential tree Qu Wenruo
2018-07-04 3:42 ` Gu, Jinxiang
2018-07-04 5:56 ` Nikolay Borisov
2018-07-04 7:37 ` Gu, Jinxiang
2018-07-03 9:10 ` [PATCH 3/5] btrfs: relocation: Only remove reloc rb_trees if reloc control has been initialized Qu Wenruo
2018-07-04 5:23 ` Gu, Jinxiang
2018-07-04 7:37 ` Gu, Jinxiang
2018-07-03 9:10 ` [PATCH 4/5] btrfs: Check each block group has corresponding chunk at mount time Qu Wenruo
2018-07-04 5:45 ` Gu, Jinxiang
2018-07-05 23:41 ` Qu Wenruo
2018-07-04 6:02 ` Nikolay Borisov
2018-07-03 9:10 ` [PATCH 5/5] btrfs: Verify every chunk has corresponding block group " Qu Wenruo
2018-07-04 6:09 ` Gu, Jinxiang
2018-07-04 7:08 ` Nikolay Borisov
2018-07-04 9:46 ` Qu Wenruo
2018-07-05 23:49 ` Qu Wenruo
2018-07-05 15:18 ` David Sterba
2018-07-05 23:44 ` Qu Wenruo
2018-07-16 13:16 ` David Sterba
2018-07-16 13:57 ` Qu Wenruo
2018-07-17 12:33 ` David Sterba
2018-07-17 13:32 ` Qu Wenruo
2018-07-19 14:22 ` David Sterba
2018-07-04 13:36 ` David Sterba [this message]
2018-07-05 1:36 ` [PATCH 0/5] Enhancement for block group/chunk verification Qu Wenruo
2018-07-05 15:18 ` David Sterba
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=20180704133607.GQ3126@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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).