From: David Sterba <dsterba@suse.cz>
To: Allison Karlitskaya <allison.karlitskaya@redhat.com>
Cc: dsterba@suse.cz, ebiggers@kernel.org, fsverity@lists.linux.dev,
linux-btrfs@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] btrfs: add FS_IOC_READ_VERITY_METADATA ioctl
Date: Tue, 26 Nov 2024 17:23:58 +0100 [thread overview]
Message-ID: <20241126162358.GL31418@twin.jikos.cz> (raw)
In-Reply-To: <20241126152331.90434-1-allison.karlitskaya@redhat.com>
On Tue, Nov 26, 2024 at 04:23:31PM +0100, Allison Karlitskaya wrote:
> 146054090b085 introduced fs-verity support for btrfs, but didn't add
Please use full reference of commits with the subject lines, like
146054090b08 ("btrfs: initial fsverity support")
The git alias command for that is below, you can name it like you want:
show -s --pretty='format:%h (\"%s\")'
> support for FS_IOC_READ_VERITY_METADATA to directly query the Merkle
> tree, descriptor and signature blocks for fs-verity enabled files.
>
> Add the (trival) implementation: we just need to wire it through to the
> fs-verity code, the same way as is done in the other two filesystems
> which support this ioctl (ext4, f2fs). The fs-verity code already has
> access to the required data.
>
> Signed-off-by: Allison Karlitskaya <allison.karlitskaya@redhat.com>
Added to for-next, thanks.
prev parent reply other threads:[~2024-11-26 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 8:41 [PATCH] btrfs: add FS_IOC_READ_VERITY_METADATA ioctl Allison Karlitskaya
2024-11-25 18:11 ` Eric Biggers
2024-11-25 20:06 ` Allison Karlitskaya
2024-11-26 2:33 ` Eric Biggers
2024-11-26 15:11 ` David Sterba
2024-11-26 15:23 ` Allison Karlitskaya
2024-11-26 16:23 ` 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=20241126162358.GL31418@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=allison.karlitskaya@redhat.com \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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