From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/2] Remove v0 extent support
Date: Mon, 25 Jun 2018 11:24:48 +0300 [thread overview]
Message-ID: <1529915090-11095-1-git-send-email-nborisov@suse.com> (raw)
It's unlikely there is anyone using that or even if they are they have bigger
problems than this patchset :). After all, v0 was introduced 9 years ago and
it was already conditionally compiled by the time BTRFS was merged in the
upstream kernel. The patches themselves are really simple - patch 1 removes
all the code within ifdef guards. Patch 2, in turn, ads graceful handling by
aborting transaction where it makes sense or calling btrfs_handle_fs_error and
printing an informative error message.
Nikolay Borisov (2):
btrfs: Remove V0 extent support
btrfs: Add graceful handling of V0 extents
fs/btrfs/ctree.c | 6 +-
fs/btrfs/ctree.h | 2 -
fs/btrfs/extent-tree.c | 239 +++++++------------------------------------------
fs/btrfs/print-tree.c | 35 ++------
fs/btrfs/relocation.c | 181 ++++++-------------------------------
5 files changed, 70 insertions(+), 393 deletions(-)
--
2.7.4
next reply other threads:[~2018-06-25 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 8:24 Nikolay Borisov [this message]
2018-06-25 8:24 ` [PATCH 1/2] btrfs: Remove V0 extent support Nikolay Borisov
2018-06-25 8:24 ` [PATCH 2/2] btrfs: Add graceful handling of V0 extents Nikolay Borisov
2018-06-25 15:21 ` David Sterba
2018-06-26 13:57 ` [PATCH v2] " Nikolay Borisov
2018-06-26 14:17 ` David Sterba
2018-06-27 13:12 ` Noah Massey
2018-06-27 13:21 ` David Sterba
2018-06-26 14:24 ` [PATCH] btrfs: annotate unlikely branches after V0 extent type removal David Sterba
2018-06-26 14:31 ` Nikolay Borisov
2018-06-26 14:43 ` David Sterba
2018-06-26 16:05 ` [PATCH v2] btrfs: Add graceful handling of V0 extents kbuild test robot
2018-06-26 17:12 ` David Sterba
2018-06-26 17:44 ` kbuild test robot
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=1529915090-11095-1-git-send-email-nborisov@suse.com \
--to=nborisov@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).