On Thu, Sep 21, 2023 at 12:30 PM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>
> On Thu, 21 Sept 2023 at 11:17, Amir Goldstein <amir73il@xxxxxxxxx> wrote:
>
> > I don't mind dropping the "inode bound" patch altogether
> > and staying with server managed backing_id without support
> > for auto-close-on-evict and only support per-file-auto-close
> > as is already implemented in my POC.
>
> Lets do that, then.
Ok. Two follow up design questions.
I used this in/out struct for both open/close ioctls,
because I needed the flags for different modes:
struct fuse_backing_map {
int32_t fd;
uint32_t flags;
uint32_t backing_id;
uint32_t padding;
};
I prefer to leave it like that (with flags=0) for future extensions
over the ioctl that inputs fd and outputs backing_id.
I hope you are ok with this.
The second thing is mmap passthrough.
I noticed that the current mmap passthough patch
uses the backing file as is, which is fine for io and does
pass the tests, but the path of that file is not a "fake path".
So either FUSE mmap passthrough needs to allocate
a backing file with "fake path"
OR if it is not important, than maybe it is not important for
overlayfs either?
Which one is it?
Do you have an idea how to dig ourselves out of this hole?
Thanks,
Amir.
