[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <339d2a18-1c5b-998b-29f5-830d8904bcb3@linux.alibaba.com>
Date: Tue, 24 Jan 2023 08:08:09 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: Giuseppe Scrivano <gscrivan@...hat.com>,
Amir Goldstein <amir73il@...il.com>
Cc: Alexander Larsson <alexl@...hat.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
david@...morbit.com, brauner@...nel.org, viro@...iv.linux.org.uk,
Vivek Goyal <vgoyal@...hat.com>,
Miklos Szeredi <miklos@...redi.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v3 0/6] Composefs: an opportunistically sharing verified
image filesystem
On 2023/1/22 17:32, Giuseppe Scrivano wrote:
> Giuseppe Scrivano <gscrivan@...hat.com> writes:
>
...
>>
>> How does validation work in EROFS for files served from fscache and that
>> are on a remote file system?
>
> nevermind my last question, I guess it would still go through the block
> device in EROFS.
> This is clearly a point in favor of a block device approach that a
> stacking file system like overlay or composefs cannot achieve without
> support from the underlying file system.
nevermind my last answer,
I was thinking with Amir's advice, you could just use FUSE+overlayfs option
for this. I wonder if such option can meet all your requirements (including
unprivileged mounts) without increasing on-disk formats in kernel to do
unprivileged mounts.
If there are still missing features, you could enhance FUSE or overlayfs.
Thanks,
Gao Xiang
Powered by blists - more mailing lists