From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v4 0/4] btrfs-progs: support for fs-verity fstests
Date: Tue, 26 Jul 2022 13:43:21 -0700 [thread overview]
Message-ID: <cover.1658867979.git.boris@bur.io> (raw)
Adding fstests for fs-verity on btrfs needs some light support from
btrfs-progs. Specifically, it needs additional device corruption
features to test corruption detection, and it needs the RO COMPAT flag.
The first patch defines (u64)-1 as "UNSET_U64"
The second patch adds corrupting arbitrary regions of item data with -I.
The third patch adds corrupting holes and prealloc in extent data.
The fourth patch includes BTRFS_FEATURE_RO_COMPAT_VERITY to ctree.h
--
v4: use ternary and get rid of "bogus_type" to cleanup input handling of
'corrupt_file_extent'
v3: add patch #defining (u64)-1 in btrfs-corrupt-block
check item bounds in corruption function
improve usage message for new corruption use case
add patch with verity ro compat flag
v2: minor cleanups from rebasing after a year
Boris Burkov (4):
btrfs-corrupt-block: define (u64)-1 as UNSET_U64
btrfs-progs: corrupt generic item data with btrfs-corrupt-block
btrfs-progs: expand corrupt_file_extent in btrfs-corrupt-block
btrfs-progs: add VERITY ro compat flag
btrfs-corrupt-block.c | 126 ++++++++++++++++++++++++++++++++++--------
kernel-shared/ctree.h | 4 +-
2 files changed, 107 insertions(+), 23 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-26 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 20:43 Boris Burkov [this message]
2022-07-26 20:43 ` [PATCH v4 1/4] btrfs-corrupt-block: define (u64)-1 as UNSET_U64 Boris Burkov
2022-07-26 20:43 ` [PATCH v4 2/4] btrfs-progs: corrupt generic item data with btrfs-corrupt-block Boris Burkov
2022-07-26 20:43 ` [PATCH v4 3/4] btrfs-progs: expand corrupt_file_extent in btrfs-corrupt-block Boris Burkov
2022-07-26 20:43 ` [PATCH v4 4/4] btrfs-progs: add VERITY ro compat flag Boris Burkov
2022-07-27 18:53 ` [PATCH v4 0/4] btrfs-progs: support for fs-verity fstests 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=cover.1658867979.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;
as well as URLs for NNTP newsgroup(s).