From: Eric Biggers <ebiggers@kernel.org>
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: send: add support for fs-verity
Date: Tue, 2 Aug 2022 13:38:37 -0700 [thread overview]
Message-ID: <YumLTcHPUL5M8rY8@sol.localdomain> (raw)
In-Reply-To: <7ac3a01572a872f8779f357598215e0e07d191bd.1659379913.git.boris@bur.io>
On Mon, Aug 01, 2022 at 11:54:40AM -0700, Boris Burkov wrote:
> +#ifdef CONFIG_FS_VERITY
> +static int send_verity(struct send_ctx *sctx, struct fs_path *path,
> + struct fsverity_descriptor *desc)
> +{
> + int ret;
> +
> + ret = begin_cmd(sctx, BTRFS_SEND_C_ENABLE_VERITY);
> + if (ret < 0)
> + goto out;
> +
> + TLV_PUT_PATH(sctx, BTRFS_SEND_A_PATH, path);
> + TLV_PUT_U8(sctx, BTRFS_SEND_A_VERITY_ALGORITHM, desc->hash_algorithm);
> + TLV_PUT_U32(sctx, BTRFS_SEND_A_VERITY_BLOCK_SIZE, 1U << desc->log_blocksize);
> + TLV_PUT(sctx, BTRFS_SEND_A_VERITY_SALT_DATA, desc->salt, desc->salt_size);
> + TLV_PUT(sctx, BTRFS_SEND_A_VERITY_SIG_DATA, desc->signature, (int)desc->sig_size);
le32_to_cpu(desc->sig_size)
> +
> + ret = send_cmd(sctx);
> +
> +tlv_put_failure:
> +out:
> + return ret;
> +}
The 'out' label is unnecessary.
> +
> +static int process_new_verity(struct send_ctx *sctx)
What does "new verity" mean in this context? The other functions called by
finish_inode_if_needed() have names like send_chown(), send_chmod(), etc., so
this name seems inconsistent (although I'm not familiar with this code).
> +
> + ret = send_verity(sctx, p, sctx->verity_descriptor);
> + if (ret < 0)
> + goto free_path;
> +
> +free_path:
> + fs_path_free(p);
The goto above is unnecessary.
> +static int process_new_verity(struct send_ctx *sctx)
> +{
> + int ret = 0;
> + struct send_ctx tmp;
> +
> + return -EPERM;
> + /* avoid unused TLV_PUT_U8 build warning without CONFIG_FS_VERITY */
> + TLV_PUT_U8(&tmp, 0, 0);
> +tlv_put_failure:
> + return -EPERM;
> +}
> +#endif
How about adding __maybe_unused to tlv_put_u##bits instead?
> @@ -8036,6 +8148,8 @@ long btrfs_ioctl_send(struct inode *inode, struct btrfs_ioctl_send_args *arg)
> kvfree(sctx->clone_roots);
> kfree(sctx->send_buf_pages);
> kvfree(sctx->send_buf);
> + if (sctx->verity_descriptor)
> + kvfree(sctx->verity_descriptor);
There's no need to check for NULL before calling kvfree().
- Eric
next prev parent reply other threads:[~2022-08-02 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 18:54 [PATCH v3] btrfs: send: add support for fs-verity Boris Burkov
2022-08-02 20:38 ` Eric Biggers [this message]
2022-08-04 14:25 ` David Sterba
2022-08-03 8:07 ` kernel test robot
2022-08-04 14:27 ` 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=YumLTcHPUL5M8rY8@sol.localdomain \
--to=ebiggers@kernel.org \
--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