Re: [fuse-devel] is release() asynchronous?

[Goswin v. B. <gos...@we...>]

"Áõ¿É¼Î" <don...@gm...> writes:

> Hi all,
>
> I am doing some personal experiments with FUSE and found a problem
> that, when I close() a file in FUSE,
> release() is triggered, but close() won't wait until release()
> returns. So I wonder if release is somehow called
> asynchronously? If so, how can I make it synchronous without
> specifying the -s command-line argument?
>
> I need to do this because I have to tell a server to do something like
> releasing a lock of the file. Now that
> in the user program if quickly re-open()s the file after close()ing
> it, the lock might have not been released
> successfully yet, which annoys me a lot.

What if a file is opened twice before being closed? Will the second
open fail?

I don't really see a difference between

Thread 1           Thread 2
open()
close()
                   open()
  [release()]
                   close()
                     [release()]

and

Thread 1           Thread 2
open()
                   open()
close()
  [release()]
                   close()
                     [release()]

MfG
        Goswin