From: Eric Biggers <ebiggers@kernel.org>
To: Richard Fung <richardfung@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/1] fuse: Add initial support for fs-verity
Date: Tue, 9 Apr 2024 19:52:54 -0400 [thread overview]
Message-ID: <20240409235254.GD1609@quark.localdomain> (raw)
In-Reply-To: <20240328205822.1007338-1-richardfung@google.com>
On Thu, Mar 28, 2024 at 08:58:21PM +0000, Richard Fung wrote:
> Hi! I am trying to add fs-verity support for virtiofs.
>
> The main complication is that fs-verity ioctls do not have constant
> iovec lengths, so simply using _IOC_SIZE like with other ioctls does not
> work.
>
> Note this doesn't include support for FS_IOC_READ_VERITY_METADATA. I
> don't know of an existing use of it and I figured it would be better
> not to include code that wouldn't be used and tested. However if you feel
> like it should be added let me know.
>
> (Also, apologies for any mistakes as this is my first Linux patch!)
>
> Richard Fung (1):
> fuse: Add initial support for fs-verity
>
> fs/fuse/ioctl.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
Just a process note: single patches should not use a cover letter. The
information should be in the patch instead, preferably in the actual commit
message but it's also possible to put text below the scissors line of the patch.
- Eric
next prev parent reply other threads:[~2024-04-09 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 20:58 [PATCH 0/1] fuse: Add initial support for fs-verity Richard Fung
2024-03-28 20:58 ` [PATCH 1/1] " Richard Fung
2024-04-02 16:16 ` Richard Fung
2024-04-09 14:50 ` Miklos Szeredi
2024-04-09 23:50 ` Eric Biggers
2024-04-11 6:06 ` Miklos Szeredi
2024-04-11 19:15 ` Richard Fung
2024-04-12 8:25 ` Miklos Szeredi
2024-04-09 23:52 ` Eric Biggers [this message]
2024-04-16 0:16 ` [PATCH v2] " Richard Fung
2024-04-19 17:05 ` Eric Biggers
2024-04-22 16:31 ` Richard Fung
2024-04-23 9:31 ` Miklos Szeredi
2024-04-23 18:41 ` Richard Fung
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=20240409235254.GD1609@quark.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=richardfung@google.com \
/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 NNTP newsgroup(s).