Linux FSCRYPT development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com,
	linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH v4] btrfs: send: add support for fs-verity
Date: Thu, 18 Aug 2022 19:32:54 +0200	[thread overview]
Message-ID: <20220818173254.GN13489@twin.jikos.cz> (raw)
In-Reply-To: <0561e8a33f991fa15053054b7b089d176fde6523.1660596577.git.boris@bur.io>

On Mon, Aug 15, 2022 at 01:54:28PM -0700, Boris Burkov wrote:
> Preserve the fs-verity status of a btrfs file across send/recv.
> 
> There is no facility for installing the Merkle tree contents directly on
> the receiving filesystem, so we package up the parameters used to enable
> verity found in the verity descriptor. This gives the receive side
> enough information to properly enable verity again. Note that this means
> that receive will have to re-compute the whole Merkle tree, similar to
> how compression worked before encoded_write.
> 
> Since the file becomes read-only after verity is enabled, it is
> important that verity is added to the send stream after any file writes.
> Therefore, when we process a verity item, merely note that it happened,
> then actually create the command in the send stream during
> 'finish_inode_if_needed'.
> 
> This also creates V3 of the send stream format, without any format
> changes besides adding the new commands and attributes.
> 
> Signed-off-by: Boris Burkov <boris@bur.io>

As for the merge target, a realistic one seems to be 6.2, we have too
many pending patches everywhere else. There's a todo list for v3 that
I'd really like to get done.

To be able to test things incrementally until then we can add v3 support
under debug config.

> --
> Changes in v4:
> - Use btrfs_get_verity_descriptor instead of verity ops get descriptor.
>   Move that definition to ctree.h for conditional building. This cleaned
>   up most of the conditional building issues, in my opinion.

Yes, that way it's ok.

> - Rename process_new_verity to process_verity.
> - Use le-to-cpu conversion for all fsverity descriptor fields.
> - Don't check NULL for kvfree of the send descriptor.

> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> --- a/fs/btrfs/send.c
> +++ b/fs/btrfs/send.c
> @@ -3,6 +3,7 @@
>   * Copyright (C) 2012 Alexander Block.  All rights reserved.
>   */
>  
> +#include "linux/compiler_attributes.h"

As Eric pointed out, this is not necessary, I'll delete the line, no
need to resend just for that.

  parent reply	other threads:[~2022-08-18 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 20:54 [PATCH v4] btrfs: send: add support for fs-verity Boris Burkov
2022-08-16  9:09 ` kernel test robot
2022-08-18  4:57 ` Eric Biggers
2022-08-18 17:40   ` David Sterba
2022-08-18 17:51     ` Eric Biggers
2022-08-18 18:29   ` Boris Burkov
2022-08-18 17:32 ` David Sterba [this message]
2022-08-18 18:49   ` Boris Burkov
2022-08-22 12:50     ` 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=20220818173254.GN13489@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