From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v2 0/2] btrfs-corrupt-block: btree data corruption
Date: Fri, 15 Jul 2022 14:22:10 -0700 [thread overview]
Message-ID: <cover.1657919808.git.boris@bur.io> (raw)
Add some more generic corruption to btrfs-corrupt-block which allows
corrupting the data in metadata items.
Motivated by testing fsverity which requires rather specific corruption
of the metadata.
The first patch adds corrupting arbitrary regions of item data with -I.
The second patch adds corrupting holes and prealloc in extent data.
--
v2: minor cleanups from rebasing after a year
Boris Burkov (2):
btrfs-progs: corrupt generic item data with btrfs-corrupt-block
btrfs-progs: expand corrupt_file_extent in btrfs-corrupt-block
btrfs-corrupt-block.c | 93 +++++++++++++++++++++++++++++++++++++++----
1 file changed, 85 insertions(+), 8 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-15 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 21:22 Boris Burkov [this message]
2022-07-15 21:22 ` [PATCH v2 1/2] btrfs-progs: corrupt generic item data with btrfs-corrupt-block Boris Burkov
2022-07-18 20:18 ` Sweet Tea Dorminy
2022-07-22 10:08 ` Nikolay Borisov
2022-07-15 21:22 ` [PATCH v2 2/2] btrfs-progs: expand corrupt_file_extent in btrfs-corrupt-block Boris Burkov
2022-07-18 16:31 ` Sweet Tea Dorminy
2022-07-22 10:14 ` Nikolay Borisov
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=cover.1657919808.git.boris@bur.io \
--to=boris@bur.io \
--cc=kernel-team@fb.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