From: Eric Biggers <ebiggers@kernel.org>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, linux-fscrypt@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [PATCH v4] fstests: add btrfs fs-verity send/recv test
Date: Fri, 19 Aug 2022 15:38:26 -0700 [thread overview]
Message-ID: <YwAQ4klC2wjpIDsf@sol.localdomain> (raw)
In-Reply-To: <c46544a9bd65f22debac5dfff0a624e3b4996ca6.1660937484.git.boris@bur.io>
On Fri, Aug 19, 2022 at 12:34:05PM -0700, Boris Burkov wrote:
> Test btrfs send/recv support for fs-verity. Includes tests for
> signatures, salts, and interaction with chmod/caps. The last of those is
> to ensure the various features that go in during inode_finalize interact
> properly.
>
> This depends on the kernel patch adding support for send:
> btrfs: send: add support for fs-verity
>
> And the btrfs-progs patch adding support for recv:
> btrfs-progs: receive: add support for fs-verity
>
> Signed-off-by: Boris Burkov <boris@bur.io>
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
prev parent reply other threads:[~2022-08-19 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 19:34 [PATCH v4] fstests: add btrfs fs-verity send/recv test Boris Burkov
2022-08-19 22:38 ` Eric Biggers [this message]
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=YwAQ4klC2wjpIDsf@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=boris@bur.io \
--cc=fstests@vger.kernel.org \
--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