Linux-FSCrypt Archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Boris Burkov <boris@bur.io>
Cc: linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH v3] btrfs-progs: receive: add support for fs-verity
Date: Wed, 21 Sep 2022 16:31:32 +0200	[thread overview]
Message-ID: <20220921143132.GH32411@twin.jikos.cz> (raw)
In-Reply-To: <3cf3573328789fcacb968f7707dc6839e44043f9.1660595824.git.boris@bur.io>

On Mon, Aug 15, 2022 at 01:54:42PM -0700, Boris Burkov wrote:
> Process an enable_verity cmd by running the enable verity ioctl on the
> file. Since enabling verity denies write access to the file, it is
> important that we don't have any open write file descriptors.
> 
> This also revs the send stream format to version 3 with no format
> changes besides the new commands and attributes.
> 
> Note: the build is conditional on the header linux/fsverity.h
> 
> Signed-off-by: Boris Burkov <boris@bur.io>

Added to devel, thanks. The v3 is still in the works and unstable so we
need to keep both sides in sync. I've added a line to configure summary
and added a line to 'btrfs receive --help' if it's compiled in.

We may also want to add an option to receive to skip verity records so
the stream can be received but without them, but that's for future once
we'll start with v3 again.

      reply	other threads:[~2022-09-21 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 20:54 [PATCH v3] btrfs-progs: receive: add support for fs-verity Boris Burkov
2022-09-21 14:31 ` David Sterba [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=20220921143132.GH32411@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=boris@bur.io \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).