From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/9] Overhaul btrfs-corrupt-block
Date: Mon, 14 May 2018 14:13:25 +0300 [thread overview]
Message-ID: <1526296414-27638-1-git-send-email-nborisov@suse.com> (raw)
btrfs-corrupt-block is a very useful tool albeit very neglected. This series
aims to give it much needed attention. There is a mix of code-improvements and
bug fixes. Code improvement mainly consists of factoring our duplicated code
(Patch 1,3,6) and improving the interface of some options (4,5,8,9). The
recurring topic here is that instead of having to pass
btrfs-corrupt-block -K <key> -f <field> -<SOME OPTION WHICH CORRUPTS AN ITEM,
POINTED TO BY K>
make each corrupting option to take the key as an argument to it. Say we want
to corrupt an item field (-I options) we now do:
btrfs-corrupt-block -I <key> -r <root> /dev/blah
instead of
btrfs-corrupt-block -I -K <key> -r <root> /dev/blah
Some patches also incorporate fixes for bugs (patch 2,7 and 9) I found during
my testing. Those usability improvements are needed to enable me to produce
tests for the pending free space tree support in userspace.
Nikolay Borisov (9):
btrfs-progs: btrfs-corrupt-block: Factor out specific-root code
btrfs-progs: btrfs-corrupt-block: Correctly handle -r when passing -I
btrfs-progs: btrfs-corrupt-block: Factor out key parsing function
btrfs-progs: btrfs-corrupt-block: Change -I flag parameter format
btrfs-progs: btrfs-corrupt-block: Convert -K flag argument handling to
common function
btrfs-progs: btrfs-corrupt-block: Factor out common "-r" handling code
btrfs-progs: btrfs-corrupt-block: Add support for handling specific
root when using -K option
btrfs-progs: btrfs-corrupt-block: Change format of -d option
btrfs-progs: btrfs-corrupt-block: Fix -D option
btrfs-corrupt-block.c | 94 +++++++++++++++++++++++++++++++--------------------
1 file changed, 57 insertions(+), 37 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-14 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 11:13 Nikolay Borisov [this message]
2018-05-14 11:13 ` [PATCH 1/9] btrfs-progs: btrfs-corrupt-block: Factor out specific-root code Nikolay Borisov
2018-05-14 11:13 ` [PATCH 2/9] btrfs-progs: btrfs-corrupt-block: Correctly handle -r when passing -I Nikolay Borisov
2018-05-14 11:13 ` [PATCH 3/9] btrfs-progs: btrfs-corrupt-block: Factor out key parsing function Nikolay Borisov
2018-05-14 11:13 ` [PATCH 4/9] btrfs-progs: btrfs-corrupt-block: Change -I flag parameter format Nikolay Borisov
2018-05-14 11:13 ` [PATCH 5/9] btrfs-progs: btrfs-corrupt-block: Convert -K flag argument handling to common function Nikolay Borisov
2018-05-14 11:13 ` [PATCH 6/9] btrfs-progs: btrfs-corrupt-block: Factor out common "-r" handling code Nikolay Borisov
2018-05-14 11:13 ` [PATCH 7/9] btrfs-progs: btrfs-corrupt-block: Add support for handling specific root when using -K option Nikolay Borisov
2018-05-14 11:13 ` [PATCH 8/9] btrfs-progs: btrfs-corrupt-block: Change format of -d option Nikolay Borisov
2018-05-14 11:13 ` [PATCH 9/9] btrfs-progs: btrfs-corrupt-block: Fix -D option Nikolay Borisov
2018-05-31 12:18 ` [PATCH 0/9] Overhaul btrfs-corrupt-block 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=1526296414-27638-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).