Documentation/filesystems/vfs.txt

133 	filesystem should be mounted
136 	should be shut down
138   owner: for internal VFS use: you should initialize this to THIS_MODULE in
141   next: for internal VFS use: you should initialize this to NULL
159 superblock must be locked.  On failure it should return ERR_PTR(error).
256 	should be synchronous or not, not all filesystems check this flag.
261 	This method should be either NULL (normal UNIX filesystem
281 	should wait until the write out has been completed. Optional.
374 	get should not have an inode (i.e. it should be a negative
381 	dentry. The "i_count" field in the inode structure should be
383 	should be inserted into the dentry (this is called a negative
387 	If you wish to overload the dentry methods then you should
442 	instances/calls of these. Filesystems should be converted to do their
524 information is attached, the PG_Private flag should be set.  This will
544 When data is written to a page, the PG_Dirty flag should be set.  It
546 should clear PG_Dirty and set PG_Writeback.  It can be actually
591       writepage should start writeout, should set PG_Writeback,
592       and should make sure the page is unlocked, either synchronously
599       should return AOP_WRITEPAGE_ACTIVATE so that the VM will not keep
605        The page will be Locked when readpage is called, and should be
623 	and that many pages should be written if possible.
633 	If defined, it should set the PageDirty flag, and the
646 	address_space should check that the write will be able to complete,
649 	storage, then those blocks should be pre-read (if they haven't been
692 	Any private data associated with the page should be updated
694 	the private data should be released, because the page
700         that the page should be freed if possible.  ->releasepage
701         should remove any private data from the page and clear the
723 	should not assume that the original address_space mapping still
724 	exists, and it should not block.
739 	and an old page to this function.  migrate_page should
821   open: called by the VFS when an inode should be opened. When the VFS
908 	blocking or storing to the dentry, d_parent and d_inode should not be
909 	used without care (because they can go NULL), instead nd->inode should
928 	Must be constant and idempotent, and should not take locks if
929 	possible, and should not or store into the dentry or inodes.
930 	Should not dereference pointers outside the dentry or inodes without
931 	lots of care (eg.  d_parent, d_inode, d_name should not be used).
953   d_dname: called when the pathname of a dentry should be generated.
958 	dcache hash, so their hash should be an invariant. As no lock is
959 	held, d_dname() should not try to modify the dentry itself, unless
966 	This should create a new VFS mount record and return the record to the
969 	VFS mount record to provide inheritable mount parameters.  NULL should
971 	the vfsmount creation failed, then an error code should be returned.
977 	the case of failure.  The vfsmount should be returned with 2 refs on
988 	past and construct the subtree there.  0 should be returned to let the
1027 	it should be cached. If it should not be cached, or if the dentry
1045 	inode structure should be set/incremented. If the inode