Re: [fuse-devel] Calls to release return immediatly?

[neuron <ne...@ho...>]

Miklos Szeredi wrote:
>>I'm dealing with compressed data, on close I write EOF to the file, and 
>>I write the file length to the file's header.  Therefore I check if the 
>>file is open when writing, to prevent multiple writes to the same file 
>>(as it would fail), and I only unlock the file on release.  So the 
>>operation above for me returns EBUSY (which is the error I return on 
>>multiple writes to the same file).
> 
> 
> I see.  Wouldn't it be nicer if you would wait on the "write lock"
> until the file is released?  That should solve this problem and at the
> same time work nicely even if there multiple writers.

Yeah I used locking in my old solution, but I rewrote it to clean it up. 
  And it's on my todo to do it this way, I was just hoping I could 
prioritize it a bit lower and wouldn't have to do it immediatly ;)

> 
> Miklos
>