[fuse-devel] flag_nullpath_ok

[Nikolaus R. <Nik...@ra...>]

Hello,

I have always been bothered by the fact that read, write etc. take not
only an inode but also a pathname as arguments, so I was quite happy to
discover the new flag_nullpath_ok.

I am using fuse 2.8.0pre3 and I have set flag_nullpath_ok = 1, but
it seems that the path is still transmitted.

Is a null-path only used under special circumstances? I had hoped I
could insert an 'assert path == NULL' into all my functions, so that the
code makes clear that file system entries are exclusively identified by
their inode.


Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C