Messages in this thread |  | | Date | Thu, 27 Sep 2001 10:52:47 +0200 | From | Jan Hudec <> | Subject | Re: Implementing a new network based file system |
| |
> Jan Harkes mentioned that getattr() don't have to be implemented (and > isn't implemented by nfs, smbfs and coda). Where do the VFS knows > about the attributes the users see? I haven't found any function in > inode_operation which gets a struct iattr* as parameter except > getattr() and setattr().
It should use getattr, but it merely reads them directly from the inode structure. You just have to keep it up-to-date
> I suppose readpage() is handled in the same way. What about syncpage?
Readpage is is similar, except there's nothing like prepare and commit read.
I have not understood syncpage yet. Maybe someone else could elighten this bit.
> I have another question about the file_operations: How is locking > (file locking => file_operations->lock()) done by the VFS. I've read > about there is a flag in the inode structure which is set by flock(). > But this lock isn't known by the server. Is file_operations->lock() > called when defined?
Have not get to this yet either.
-------------------------------------------------------------------------------- - Jan Hudec `Bulb' <bulb@ucw.cz> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |