From: Miklos Szeredi <miklos@szeredi.hu>
To: Richard Fung <richardfung@google.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel@vger.kernel.org, fsverity@lists.linux.dev
Subject: Re: [PATCH 1/1] fuse: Add initial support for fs-verity
Date: Fri, 12 Apr 2024 10:25:34 +0200 [thread overview]
Message-ID: <CAJfpegvt4ivELbyF-4qBRUX7wLxSCwpZ7fg2o7Kry-_gF3kRYg@mail.gmail.com> (raw)
In-Reply-To: <CAGndiTMNuzKot7fKSE5Hrcm=9XQ-0=KsQCnt4wXVtkq0bmVvXg@mail.gmail.com>
On Thu, 11 Apr 2024 at 21:16, Richard Fung <richardfung@google.com> wrote:
> Would allowing FUSE_IOCTL_RETRY for these specific ioctls be
> possible/preferable? From my limited understanding retrying is
> designed to handle dynamically sized data. However it seems like
> that's currently only allowed for CUSE.
>
> If that's not a good idea then I'll try to split it into a separate
> function if you don't feel strongly about the other approach.
It's not a good idea, because it gives complete freedom to the fuse
server about where to gather data from, and that's just an invitation
to malicious behavior.
So yes, please split the current one off to a separate function and
let's see how that looks.
Thanks,
Miklos
next prev parent reply other threads:[~2024-04-12 8:25 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 [this message]
2024-04-09 23:52 ` [PATCH 0/1] " Eric Biggers
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=CAJfpegvt4ivELbyF-4qBRUX7wLxSCwpZ7fg2o7Kry-_gF3kRYg@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--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).