On Mon, Oct 21, 2024 at 3:15 AM Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > > On Fri, 18 Oct 2024 at 07:31, Shakeel Butt <shakeel.butt@xxxxxxxxx> wrote: > > > I feel like this is too much restrictive and I am still not sure why > > blocking on fuse folios served by non-privileges fuse server is worse > > than blocking on folios served from the network. > > Might be. But historically fuse had this behavior and I'd be very > reluctant to change that unconditionally. > > With a systemwide maximal timeout for fuse requests it might make > sense to allow sync(2), etc. to wait for fuse writeback. > > Without a timeout allowing fuse servers to block sync(2) indefinitely > seems rather risky. Could we skip waiting on writeback in sync(2) if it's a fuse folio? That seems in line with the sync(2) documentation Jingbo referenced earlier where it states "The writing, although scheduled, is not necessarily complete upon return from sync()." https://pubs.opengroup.org/onlinepubs/9699919799/functions/sync.html Thanks, Joanne > > Thanks, > Miklos
