From: Eric Biggers <ebiggers@kernel.org>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
kernel-team@fb.com, linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH] fstests: add btrfs fs-verity send/recv test
Date: Wed, 17 Aug 2022 22:12:06 -0700 [thread overview]
Message-ID: <Yv3KJtM7L1CsIkVz@sol.localdomain> (raw)
In-Reply-To: <9e0ee6345a406765cf06594b805cb3568de16acc.1660596985.git.boris@bur.io>
On Mon, Aug 15, 2022 at 01:57:56PM -0700, Boris Burkov wrote:
> diff --git a/tests/btrfs/271 b/tests/btrfs/271
> new file mode 100755
> index 00000000..93b34540
> --- /dev/null
> +++ b/tests/btrfs/271
There is already a btrfs/271, so this patch doesn't apply anymore. Best to use
a higher number and let the maintainer renumber the test when applying.
> @@ -0,0 +1,114 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2022 YOUR NAME HERE. All Rights Reserved.
YOUR NAME HERE is a great company to work for :-)
> +_require_test
I don't see where this uses the test filesystem; it seems to use scratch only.
> + if [ $salt -eq 1 ]; then
> + extra_args+=" --salt=deadbeef"
> + fi
I like to use true and false for this sort of thing so you can just do:
if $salt; then
> + echo "check received subvolume..."
> + echo 3 > /proc/sys/vm/drop_caches
A comment explaining why the drop_caches is needed would be helpful.
And should there be a sync before it, and should it be _scratch_cycle_mount?
> + _fsv_measure $fsv_file > $tmp.digest-after
> + $GETCAP_PROG $fsv_file > $tmp.cap-after
> + diff $tmp.digest-before $tmp.digest-after
> + diff $tmp.cap-before $tmp.cap-after
> + _scratch_unmount
> + echo OK
Should this compare the file's contents too?
- Eric
next prev parent reply other threads:[~2022-08-18 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 20:57 [PATCH] fstests: add btrfs fs-verity send/recv test Boris Burkov
2022-08-18 5:12 ` Eric Biggers [this message]
2022-08-18 19:38 ` Boris Burkov
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 23:49 Boris Burkov
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=Yv3KJtM7L1CsIkVz@sol.localdomain \
--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