From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: Re: [PATCH 0/3] Introduce comprehensive sanity check framework and
Date: Tue, 22 Aug 2017 13:58:55 +0300 [thread overview]
Message-ID: <2d3b55a3-8308-fd63-1d97-f94f19a85235@suse.com> (raw)
In-Reply-To: <20170822073717.13081-1-quwenruo.btrfs@gmx.com>
On 22.08.2017 10:37, Qu Wenruo wrote:
> The patchset introduce a new framework to do more comprehensive (if not
> the most) sanity check when reading out a leaf.
>
> The new sanity checker will include:
>
> 1) Key order
> Existing code
>
> 2) Item boundary
> Existing code with enhanced checker to ensure item pointer doesn't
> overlap with item itself.
>
> 3) Key type based sanity checker
> Only EXTENT_DATA checker is implemented yet.
> As each checker should go through review and tests, or it can easily
> make a valid btrfs failed to be mounted.
> So only one checker is implemented as an example.
>
> Existing checker like INODE_REF checker can be moved to this
> framework easily, and we can centralize all existing checkers, make
> the rest of codes more clean.
>
> Performance wise, it's just iterating a leaf.
> And it will only get triggered when read out a leaf, cached leaf will
> not go through such checker.
> So it won't be a performance breaker.
>
> I tested with the patchset applied on v4.13-rc6 with fstests, no
> regression is detected.
>
> Qu Wenruo (3):
> btrfs: Refactor check_leaf function for later expansion.
> btrfs: Check if item pointer overlap with item itself
> btrfs: Add sanity check for EXTENT_DATA when reading out leaf
I have one minor comment on 3/3 which I've sent separately but otherwise
this series looks good and I like the direction it's steering future
code into.
For the whole series:
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>
> fs/btrfs/disk-io.c | 137 ++++++++++++++++++++++++++++++++++------
> include/uapi/linux/btrfs_tree.h | 1 +
> 2 files changed, 119 insertions(+), 19 deletions(-)
>
prev parent reply other threads:[~2017-08-22 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 7:37 [PATCH 0/3] Introduce comprehensive sanity check framework and Qu Wenruo
2017-08-22 7:37 ` [PATCH 1/3] btrfs: Refactor check_leaf function for later expansion Qu Wenruo
2017-08-22 7:37 ` [PATCH 2/3] btrfs: Check if item pointer overlap with item itself Qu Wenruo
2017-08-22 7:37 ` [PATCH 3/3] btrfs: Add sanity check for EXTENT_DATA when reading out leaf Qu Wenruo
2017-08-22 10:57 ` Nikolay Borisov
2017-08-22 11:00 ` Nikolay Borisov
2017-08-22 11:23 ` Qu Wenruo
2017-08-22 11:38 ` Nikolay Borisov
2017-08-22 10:58 ` Nikolay Borisov [this message]
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=2d3b55a3-8308-fd63-1d97-f94f19a85235@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).