On Sun, Sep 16, 2018 at 12:35 AM, Oleg Chernovskiy <kanedias@xxxxxxxx> wrote: > Hi, > > > I'm writing primarily because of the bug users are reporting > > in my network-based filesystem [1]. In short, rsync first creates temporary file, > > flushes and closes it and then immediately opens it again. The problem is, > > sometimes I see that afterwards it tries to write to a closed fd resulting in IO error. > > > Is there a possibility that FUSE can execute fresh OPEN call before pending RELEASE > > for the same inode that was processed? Yes. > > > I see OPEN calls are always sync in fuse_open_common but RELEASE seems to be > > async as I see it goes to background queue in > > fuse_release_common->fuse_file_put->fuse_request_send_background, can this be the reason? Right. > > > Is there something that I'm missing? Maybe it's me implementing fs in wrong way? > > How is this kind of behavior is corrected? I don't quite get what the problem is. The filesystem needs to handle multiple parallel open instances of the same inode anyway. What's special about this case of two slightly overlapping open instances as opposed to two fully overlapping open instances? Thanks, Miklos
