From: Alessio Balsini <balsini@android.com>
To: Antonio SJ Musumeci <trapexit@spawn.link>
Cc: Alessio Balsini <balsini@android.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Akilesh Kailash <akailash@google.com>,
Amir Goldstein <amir73il@gmail.com>,
David Anderson <dvander@google.com>,
Eric Yan <eric.yan@oneplus.com>, Jann Horn <jannh@google.com>,
Jens Axboe <axboe@kernel.dk>, Martijn Coenen <maco@android.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Lawrence <paullawrence@google.com>,
Stefano Duo <stefanoduo@google.com>,
Zimuzo Ezeozue <zezeozue@google.com>,
fuse-devel@lists.sourceforge.net, kernel-team@android.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [fuse-devel] [PATCH V8 0/3] fuse: Add support for passthrough read/write
Date: Fri, 18 Sep 2020 17:03:58 +0100 [thread overview]
Message-ID: <20200918160358.GA3385065@google.com> (raw)
In-Reply-To: <21e1b3be-6cc1-c73a-4e3e-963e2dd64f1f@spawn.link>
Hi Antonio,
It's indeed a great idea to notify the FUSE daemon in case of lower file
system exceptions, otherwise transparent when passthrough is enabled.
I was already planning to work on this feature as a future extension, glad
to see that this is of interest to the community.
Thanks for your feedback,
Alessio
On Fri, Sep 11, 2020 at 02:46:04PM -0400, Antonio SJ Musumeci wrote:
> On 9/11/2020 12:34 PM, Alessio Balsini via fuse-devel wrote:
> > Add support for file system passthrough read/write of files when enabled in
> > userspace through the option FUSE_PASSTHROUGH.
> Might be more effort than it is worth but any thoughts on userland error
> handling for passthrough? My use case, optionally, responds to read or write
> errors in particular ways. It's not an unreasonable tradeoff to disable
> passthrough if the user wants those features but was wondering if there was
> any consideration of extending the protocol to pass read/write errors back
> to the fuse server.
prev parent reply other threads:[~2020-09-18 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 16:34 [PATCH V8 0/3] fuse: Add support for passthrough read/write Alessio Balsini
2020-09-11 16:34 ` [PATCH V8 1/3] fuse: Definitions and ioctl() for passthrough Alessio Balsini
2020-09-11 20:01 ` kernel test robot
2020-09-11 20:01 ` [RFC PATCH] fuse: fuse_passthrough_open() can be static kernel test robot
2020-09-11 20:40 ` [PATCH V8 1/3] fuse: Definitions and ioctl() for passthrough kernel test robot
2020-09-12 11:06 ` Amir Goldstein
2020-09-18 16:33 ` Alessio Balsini
2020-09-18 19:59 ` Amir Goldstein
2020-09-22 12:15 ` Alessio Balsini
2020-09-22 16:08 ` Amir Goldstein
2020-09-29 14:30 ` Alessio Balsini
2020-09-11 16:34 ` [PATCH V8 2/3] fuse: Introduce synchronous read and write " Alessio Balsini
2020-09-12 9:55 ` Amir Goldstein
2020-09-21 11:01 ` Alessio Balsini
2020-09-21 13:07 ` Amir Goldstein
2020-09-11 16:34 ` [PATCH V8 3/3] fuse: Handle AIO read and write in passthrough Alessio Balsini
2020-09-11 17:23 ` Jens Axboe
2020-09-21 15:28 ` Alessio Balsini
2020-09-11 18:46 ` [fuse-devel] [PATCH V8 0/3] fuse: Add support for passthrough read/write Antonio SJ Musumeci
2020-09-18 16:03 ` Alessio Balsini [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=20200918160358.GA3385065@google.com \
--to=balsini@android.com \
--cc=akailash@google.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=dvander@google.com \
--cc=eric.yan@oneplus.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jannh@google.com \
--cc=kernel-team@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=miklos@szeredi.hu \
--cc=palmer@dabbelt.com \
--cc=paullawrence@google.com \
--cc=stefanoduo@google.com \
--cc=trapexit@spawn.link \
--cc=zezeozue@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.