Re: [fuse-devel] Problem with open/close sequence

[John A. K. Jr. <ja...@j-...>]

> Sometimes we get open followed by another open which generates an error
> indicating the file is already open.
>
> If we put a delay of say 100ms after the close operation then the
> problem goes away. It appears to be a sequencing problem at the fuse
> level.
>
> Can anyone shed any light on this particular problem

You do realize libFUSE uses threads, right? Which is good, because 
otherwise only one process on the entire box could be using a filesystem 
at a time.

I suggest that if one program has a file open and another one wants to 
open one, you should block the process instead of generating an error. 
That would give time for the thread handling the close() to complete, 
followed by handling the open().