Documentation/filesystems/vfs.rst

97 namespace, the VFS will call the appropriate mount() method for the
99 ->mount() will be attached to the mountpoint, so that when pathname
100 resolution reaches the mountpoint it will jump into the root of that
263 	alloc_inode will be used to allocate a larger structure which
350 	encountered, hence the void return type.  This will never be
357 	about whether implementations will cause holdoff problems due to
449 	you will probably call d_instantiate() with the dentry and the
461 	calls like create(2), mknod(2), mkdir(2) and so on will fail.
469 	support hard links.  You will probably need to call
478 	to support symlinks.  You will probably need to call
483 	to support creating subdirectories.  You will probably need to
493 	you want to support creating these types of inodes.  You will
520 	destructor, argument).  In that case destructor(argument) will
536 	->get_link for symlinks and readlink(2) will automatically use
549 	-ECHILD and it will be called again in ref-walk mode.
565 	an inode.  If this is not defined the VFS will update the inode
605 Clean pages without PagePrivate and with no external references will be
629 information is attached, the PG_Private flag should be set.  This will
665 Most applications that do buffered I/O will periodically call a file
683 multiple writers, all of them will get back an error on a subsequent
753 	should return AOP_WRITEPAGE_ACTIVATE so that the VM will not
760 	will be Locked when readpage is called, and should be unlocked
764 	the page will be relocated, relocked and if that all succeeds,
765 	->readpage will be called again.
770 	the writeback_control will specify a range of pages that must be
774 	This will choose pages from the address space that are tagged as
775 	DIRTY and will pass them to ->writepage.
789 	after starting I/O on each page.  Usually the page will be
792 	window, it can simply return.  The caller will decrement the page
795 	will be ignored; simply unlock the page if an I/O error occurs.
803 	This interface is deprecated and will be removed by the end of
809 	The address_space should check that the write will be able to
811 	internal housekeeping.  If the write will update parts of any
853 	If a page has PagePrivate set, then invalidatepage will be
857 	space (in the latter case 'offset' will always be 0 and 'length'
858 	will be PAGE_SIZE).  Any private data associated with the page
873 	->releasepage succeeds, the page will be removed from the
883 	releasepage will need to ensure this.  Possibly it can clear the
907 	signalling imminent failure) it will pass a new page and an old
1128 (character or block special) most filesystems will call special
1129 support routines in the VFS which will locate the required device
1189 	-ECHILD and it will be called again in ref-walk mode.
1200 	As with d_revalidate, most local filesystems will set this to
1228 	and inodes won't disappear, neither will our sb or filesystem
1287 	the directory will be treated as an ordinary directory and
1290 	If a vfsmount is returned, the caller will attempt to mount it
1291 	on the mountpoint and will remove the vfsmount from its
1294 	caller will clean up the additional ref.
1308 	the automount flag.  Any other error code will abort pathwalk
1357 	call to dput() will deallocate the dentry if its usage count