Lines Matching refs:VFS
21 VFS system calls open(2), stat(2), read(2), write(2), chmod(2) and so on
29 The VFS implements the open(2), stat(2), chmod(2), and similar system
30 calls. The pathname argument that is passed to them is used by the VFS
39 dentry, the VFS may have to resort to creating dentries along the way,
54 To look up an inode requires that the VFS calls the lookup() method of
56 filesystem implementation that the inode lives in. Once the VFS has the
59 stat(2) operation is fairly simple: once the VFS has the dentry, it
72 this is another switch performed by the VFS. The file structure is
75 Reading, writing and closing files (and other assorted VFS operations)
79 dentry in use, which in turn means that the VFS inode is still in use.
97 namespace, the VFS will call the appropriate mount() method for the
145 for internal VFS use: you should initialize this to THIS_MODULE
149 for internal VFS use: you should initialize this to NULL
224 This describes how the VFS can manipulate the superblock of your
273 this method is called by the VFS to mark an inode dirty.
276 this method is called when the VFS needs to write an inode to
294 called when the VFS wants to delete an inode
297 called when the VFS wishes to free the superblock
301 called when VFS is writing out all dirty data associated with a
306 called when VFS is locking a filesystem and forcing it into a
311 called when VFS is unlocking a filesystem and making it writable
315 called when the VFS needs to get filesystem statistics.
322 called then the VFS clears the inode. Optional
325 called when the VFS is unmounting a filesystem.
328 called by the VFS to show mount options for /proc/<pid>/mounts.
332 called by the VFS to read from filesystem quota file.
335 called by the VFS to write to filesystem quota file.
355 any scanning loop that is done. This allows the VFS to
388 Called by the VFS to get the value of a particular extended
393 Called by the VFS to set the value of a particular extended
412 This describes how the VFS can manipulate an inode in your filesystem.
453 called when the VFS needs to look up an inode in a parent
505 replacing the target. The VFS already checks for existence, so
509 exist; this is checked by the VFS. Unlike plain rename, source
513 called by the VFS to follow a symbolic link to the inode it
521 be called once VFS is done with the body you've returned. May
527 VFS may use it directly without calling ->get_link(); however,
540 called by the VFS to check for access rights on a POSIX-like
552 called by the VFS to set attributes for a file. This method is
556 called by the VFS to get attributes of a file. This method is
560 called by the VFS to list all extended attributes for a given
564 called by the VFS to update a specific time or the i_version of
565 an inode. If this is not defined the VFS will update the inode
699 This describes how the VFS can manipulate mapping of a file to page
844 called by the VFS to map a logical block offset within object to
963 This describes how the VFS can manipulate an open file. As of kernel
1012 called when the VFS needs to move the file position index
1030 called when the VFS needs to read the directory contents
1033 called when the VFS needs to read the directory contents when
1037 called by the VFS when a process wants to check if there is
1052 called by the VFS when an inode should be opened. When the VFS
1090 called by the VFS to splice data from a pipe to a file. This
1094 called by the VFS to splice data from file to a pipe. This
1098 called by the VFS to set or release a file lock lease. setlease
1103 called by the VFS to preallocate blocks or punch a hole.
1129 support routines in the VFS which will locate the required device
1145 operations. Dentries and the dcache are the domain of the VFS and the
1148 the VFS uses a default. As of kernel 2.6.22, the following members are
1170 called when the VFS needs to revalidate a dentry. This is
1192 called when the VFS needs to revalidate a "jumped" dentry. This
1209 called when the VFS adds a dentry to the hash table. The first
1249 deallocated). The default when this is NULL is that the VFS
1280 This should create a new VFS mount record and return the record
1283 and the parent VFS mount record to provide inheritable mount
1439 A tour of the Linux VFS by Michael K. Johnson. 1996