From: Jean-Pierre A. <jea...@wa...> - 2010-10-13 10:54:41
|
Hi, Gal Rosen wrote: > Hi Stef, > > The still something that I do not understand. > Most of the low level interface functions are comes with fuse_ino_t, and > some like look_up, mknod, create are comes with parent fuse_ino_t and name. > Is there any syscall in libc that can extract the path from the inode, and > also extract the path from parent inode and name ? > Because in order to work on the file I must have the path, or maybe there > is syscalls in libc that work on the inode ? > The very problem here, is a file can have several paths (when it is hard linked). In that situation, which patch are you expecting ? To get the path, you have to keep track of the successive lookup calls. I think this is what the high level does. I am even not sure that the high level cannot guarantee that the path sent to the driver is the same as the one the application requested. The fuse user-space library probably only gets inode numbers from the kernel module and it has to translate them to paths. Correct me if I am wrong. (In general this does not matter, but when wanting to associate a short 8+3 name to an existing long name, I have to put it in the path the application requested). Regards Jean-Pierre |