On Wed 27-10-21 08:59:15, Amir Goldstein wrote: > On Tue, Oct 26, 2021 at 10:14 PM Ioannis Angelakopoulos > <iangelak@xxxxxxxxxx> wrote: > > On Tue, Oct 26, 2021 at 2:27 PM Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > > The problem here is that the OPEN event might still be travelling towards the guest in the > > virtqueues and arrives after the guest has already deleted its local inode. > > While the remote event (OPEN) received by the guest is valid, its fsnotify > > subsystem will drop it since the local inode is not there. > > > > I have a feeling that we are mixing issues related to shared server > and remote fsnotify. I don't think Ioannis was speaking about shared server case here. I think he says that in a simple FUSE remote notification setup we can loose OPEN events (or basically any other) if the inode for which the event happens gets deleted sufficiently early after the event being generated. That seems indeed somewhat unexpected and could be confusing if it happens e.g. for some directory operations. Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
