From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: map-logical: remove the extent check
Date: Thu, 12 Aug 2021 13:35:04 +0800 [thread overview]
Message-ID: <20210812053508.175737-1-wqu@suse.com> (raw)
Commit eb81f8d263ce ("btrfs-progs: map-logical: Rework map-logical
logics") introduced a strict extent item check for btrfs-map-logical.
It not only makes it harder to use btrfs-map-logical, but also prevents
btrfs-map-logical to handle fs with corrupted extent tree.
This patchset will address the behavior by completely removing the
extent item check, and allow btrfs-map-logical to work on fs with
corrupted extent tree.
Since we're here, also change the default mapping length to sectorsize,
and reject any unaligned logical/bytes pair.
Qu Wenruo (4):
btrfs-progs: map-logical: use sectorsize as default size
btrfs-progs: map-logical: reject unaligned logical/bytes pair
btrfs-progs: map-logical: loosen the required trees to open the
filesystem
btrfs-progs: map-logical: remove the extent item check
btrfs-map-logical.c | 158 +++++---------------------------------------
1 file changed, 17 insertions(+), 141 deletions(-)
--
2.32.0
next reply other threads:[~2021-08-12 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 5:35 Qu Wenruo [this message]
2021-08-12 5:35 ` [PATCH 1/4] btrfs-progs: map-logical: use sectorsize as default size Qu Wenruo
2021-08-12 5:35 ` [PATCH 2/4] btrfs-progs: map-logical: reject unaligned logical/bytes pair Qu Wenruo
2021-08-12 6:42 ` Nikolay Borisov
2021-08-12 5:35 ` [PATCH 3/4] btrfs-progs: map-logical: loosen the required trees to open the filesystem Qu Wenruo
2021-08-12 6:41 ` Nikolay Borisov
2021-08-12 5:35 ` [PATCH 4/4] btrfs-progs: map-logical: remove the extent item check 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=20210812053508.175737-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