From: Eric Biggers <ebiggers@kernel.org>
To: Boris Burkov <boris@bur.io>
Cc: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v7 1/5] verity: require corruption functionality
Date: Wed, 16 Mar 2022 17:21:18 +0000 [thread overview]
Message-ID: <YjIcjiHLwTENvqZe@gmail.com> (raw)
In-Reply-To: <73ea99df928e64baf172fa38a0648fb21494e864.1647382272.git.boris@bur.io>
On Tue, Mar 15, 2022 at 03:15:57PM -0700, Boris Burkov wrote:
> Corrupting ext4 and f2fs relies on xfs_io fiemap. Btrfs corruption
> testing will rely on a btrfs specific corruption utility. Add the
> ability to require corruption functionality to make this properly
> modular. To start, just check for fiemap, as that is needed
> universally for _fsv_scratch_corrupt_bytes.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
> ---
> common/verity | 6 ++++++
> tests/generic/574 | 1 +
> tests/generic/576 | 1 +
> 3 files changed, 8 insertions(+)
>
> diff --git a/common/verity b/common/verity
> index 38eea157..1afe4a82 100644
> --- a/common/verity
> +++ b/common/verity
> @@ -141,6 +141,12 @@ _require_fsverity_dump_metadata()
> _fail "Unexpected output from 'fsverity dump_metadata': $(<"$tmpfile")"
> }
>
> +# Check for userspace tools needed to corrupt verity data or metadata.
> +_require_fsverity_corruption()
> +{
> + _require_xfs_io_command "fiemap"
> +}
> +
> _scratch_mkfs_verity()
> {
> case $FSTYP in
> diff --git a/tests/generic/574 b/tests/generic/574
> index 882baa21..17fdea52 100755
> --- a/tests/generic/574
> +++ b/tests/generic/574
> @@ -28,6 +28,7 @@ _cleanup()
> _supported_fs generic
> _require_scratch_verity
> _disable_fsverity_signatures
> +_require_fsverity_corruption
>
> _scratch_mkfs_verity &>> $seqres.full
> _scratch_mount
> diff --git a/tests/generic/576 b/tests/generic/576
> index 82fbdd71..d3e0a2d6 100755
> --- a/tests/generic/576
> +++ b/tests/generic/576
> @@ -28,6 +28,7 @@ _supported_fs generic
> _require_scratch_verity
> _require_scratch_encryption
> _require_command "$KEYCTL_PROG" keyctl
> +_require_fsverity_corruption
> _disable_fsverity_signatures
>
> _scratch_mkfs_encrypted_verity &>> $seqres.full
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2022-03-16 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 22:15 [PATCH v7 0/5] tests for btrfs fsverity Boris Burkov
2022-03-15 22:15 ` [PATCH v7 1/5] verity: require corruption functionality Boris Burkov
2022-03-16 17:21 ` Eric Biggers [this message]
2022-03-15 22:15 ` [PATCH v7 2/5] btrfs: test btrfs specific fsverity corruption Boris Burkov
2022-03-16 17:26 ` Eric Biggers
2022-03-16 17:36 ` Boris Burkov
2022-03-15 22:15 ` [PATCH v7 3/5] generic/574: corrupt btrfs merkle tree data Boris Burkov
2022-03-16 17:29 ` Eric Biggers
2022-03-15 22:16 ` [PATCH v7 4/5] btrfs: test verity orphans with dmlogwrites Boris Burkov
2022-03-15 22:16 ` [PATCH v7 5/5] generic: test fs-verity EFBIG scenarios Boris Burkov
2022-03-16 17:30 ` Eric Biggers
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=YjIcjiHLwTENvqZe@gmail.com \
--to=ebiggers@kernel.org \
--cc=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@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).