[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21e1b3be-6cc1-c73a-4e3e-963e2dd64f1f@spawn.link>
Date: Fri, 11 Sep 2020 14:46:04 -0400
From: Antonio SJ Musumeci <trapexit@...wn.link>
To: Alessio Balsini <balsini@...roid.com>,
Miklos Szeredi <miklos@...redi.hu>
Cc: Akilesh Kailash <akailash@...gle.com>,
Amir Goldstein <amir73il@...il.com>,
David Anderson <dvander@...gle.com>,
Eric Yan <eric.yan@...plus.com>, Jann Horn <jannh@...gle.com>,
Jens Axboe <axboe@...nel.dk>,
Martijn Coenen <maco@...roid.com>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Lawrence <paullawrence@...gle.com>,
Stefano Duo <stefanoduo@...gle.com>,
Zimuzo Ezeozue <zezeozue@...gle.com>,
fuse-devel@...ts.sourceforge.net, kernel-team@...roid.com,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [fuse-devel] [PATCH V8 0/3] fuse: Add support for passthrough
read/write
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.
Powered by blists - more mailing lists