Re: [fuse-devel] ENOENT from link()

[Miklos S. <mi...@sz...>]

Boris Protopopov <bpr...@ho...> writes:

> So, what could be happening is that the dentry with "file2" name is
> somehow turned to a negative dentry as a result of the
> unlink("file1"), and if I force re-lookup() either by setting
> entry_timeout to zero or by issuing that lookup explicitly, things are
> fine.

See patch by Anand Avati and the related discussion (I added you to the
CC list).

> I also tried using fuse_lowlevel_notify_inval_entry(), but my
> filesystem hangs. I tried issuing fuse_lowlevel_notify_inval_entry()
> before or after the fuse_reply_entry() in the link() handler; it hangs
> in both cases.

These notifications should not be called from filesystem callbacks
because that may deadlock.  

>  Can someone help explain what the proper use of this notification
> callback is ?

The purpose of these notifications is to asynchronously notify the
kernel of changes (e.g. the file was modified on a remote server).

Thanks,
Miklos