From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/6] btrfs: Enhanced validation check for fuzzed images
Date: Wed, 1 Aug 2018 10:37:15 +0800 [thread overview]
Message-ID: <20180801023721.32143-1-wqu@suse.com> (raw)
The branch can be fetched from the following git repo:
https://github.com/adam900710/linux/tree/tree_checker_enhance
It's based on v4.18-rc1, with 3 patches already merged into misc-next.
This patchset introduced the following enhanced validation check:
1) chunk/block group/dev extent cross check
Unlike extent tree, such cross check can be implemented pretty easy
with minimal mount time impact.
Now the kernel could do chunk/bg/dev extent check as good as btrfs
check.
2) Locking test to avoid possible deadlock due to extent tree corruption
Unfortunately, for extent tree we can't do really much cross check.
Instead we use the selftest from btrfs_tree_lock() to detect and
avoid deadlock caused by corrupted extent tree.
The 3rd patch "btrfs: Remove unused function btrfs_account_dev_extents_size()"
has also been merged into misc-next.
changelog:
v2:
Added reviewed-by tags from Gu and Nikolay.
Address comment from David for the 4th patch
Address comment from Gu for the 2nd patch.
Qu Wenruo (6):
btrfs: Check each block group has corresponding chunk at mount time
btrfs: Verify every chunk has corresponding block group at mount time
btrfs: Remove unused function btrfs_account_dev_extents_size()
btrfs: Introduce mount time chunk <-> dev extent mapping check
btrfs: Exit gracefully when failed to add chunk map
btrfs: locking: Allow btrfs_tree_lock() to return error to avoid
deadlock
fs/btrfs/ctree.c | 57 ++++++--
fs/btrfs/disk-io.c | 7 +
fs/btrfs/extent-tree.c | 114 +++++++++++++--
fs/btrfs/extent_io.c | 8 +-
fs/btrfs/free-space-tree.c | 4 +-
fs/btrfs/locking.c | 13 +-
fs/btrfs/locking.h | 2 +-
fs/btrfs/qgroup.c | 4 +-
fs/btrfs/relocation.c | 13 +-
fs/btrfs/tree-log.c | 14 +-
fs/btrfs/volumes.c | 276 +++++++++++++++++++++++++------------
fs/btrfs/volumes.h | 4 +-
12 files changed, 397 insertions(+), 119 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-01 4:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 2:37 Qu Wenruo [this message]
2018-08-01 2:37 ` [PATCH v2 1/6] btrfs: Check each block group has corresponding chunk at mount time Qu Wenruo
2018-08-01 2:54 ` Su Yue
2018-08-01 2:37 ` [PATCH v2 2/6] btrfs: Verify every chunk has corresponding block group " Qu Wenruo
2018-08-01 2:37 ` [PATCH v2 3/6] btrfs: Remove unused function btrfs_account_dev_extents_size() Qu Wenruo
2018-08-01 2:37 ` [PATCH v2 4/6] btrfs: Introduce mount time chunk <-> dev extent mapping check Qu Wenruo
2018-08-01 3:18 ` Su Yue
2019-01-14 11:09 ` Filipe Manana
2019-01-14 11:28 ` Qu Wenruo
2018-08-01 2:37 ` [PATCH v2 5/6] btrfs: Exit gracefully when failed to add chunk map Qu Wenruo
2018-08-01 2:37 ` [PATCH v2 6/6] btrfs: locking: Allow btrfs_tree_lock() to return error to avoid deadlock Qu Wenruo
2018-08-01 2:55 ` Su Yue
2018-08-02 16:40 ` [PATCH v2 0/6] btrfs: Enhanced validation check for fuzzed images David Sterba
2018-08-03 0:06 ` Qu Wenruo
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=20180801023721.32143-1-wqu@suse.com \
--to=wqu@suse.com \
--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).