Lines Matching full:filesystem
16 The Virtual File System (also known as the Virtual Filesystem Switch) is
17 the software layer in the kernel that provides the filesystem interface
19 kernel which allows different filesystem implementations to coexist.
22 are called from a process context. Filesystem locking is described in
47 filesystem objects such as regular files, directories, FIFOs and other
56 filesystem implementation that the inode lives in. Once the VFS has the
71 specific filesystem implementation can do its work. You can see that
82 Registering and Mounting a Filesystem
85 To register and unregister a filesystem, use the following API
95 The passed struct file_system_type describes your filesystem. When a
96 request is made to mount a filesystem onto a directory in your
98 specific filesystem. New vfsmount referring to the tree returned by
110 This describes the filesystem. As of kernel 2.6.39, the following
129 the name of the filesystem type, such as "ext2", "iso9660",
136 the method to call when a new instance of this filesystem should
140 the method to call when an instance of this filesystem should be
156 describes the filesystem, partly initialized by the specific
157 filesystem code
174 on filesystem type. E.g. for block filesystems, dev_name is interpreted
176 suitable filesystem image the method creates and initializes struct
179 ->mount() may choose to return a subtree of existing filesystem - it
186 super_operations" which describes the next level of the filesystem
189 Usually, a filesystem uses one of the generic mount() implementations
193 mount a filesystem residing on a block device
196 mount a filesystem that is not backed by a device
199 mount a filesystem which shares the instance between all mounts
218 A superblock object represents a mounted filesystem.
225 filesystem. As of kernel 2.6.22, the following members are defined:
287 This method should be either NULL (normal UNIX filesystem
309 called when VFS is locking a filesystem and forcing it into a
314 called when VFS is unlocking a filesystem and making it writable
318 called when the VFS needs to get filesystem statistics.
321 called when the filesystem is remounted. This is called with
328 called when the VFS is unmounting a filesystem.
335 called by the VFS to read from filesystem quota file.
338 called by the VFS to write to filesystem quota file.
341 called by the sb cache shrinking function for the filesystem to
346 called by the sb cache shrinking function for the filesystem to
348 Optional, but any filesystem implementing this method needs to
352 We can't do anything with any errors that the filesystem might
401 When none of the xattr handlers of a filesystem match the specified
402 attribute name or when a filesystem doesn't support extended attributes,
409 An inode object represents an object within the filesystem.
415 This describes how the VFS can manipulate an inode in your filesystem.
508 The filesystem must return -EINVAL for any unsupported or
533 If the filesystem stores the symlink target in ->i_link, the
548 filesystem.
551 rcu-walk mode, the filesystem must check the permission without
577 method the filesystem can look up, possibly create and open the
580 symlink, device, or just something filesystem won't do atomic
719 cache in your filesystem. The following members are defined:
809 unlocked by the I/O completion handler. If the filesystem decides
826 Called by the generic buffered write code to ask the filesystem
835 The filesystem must return the locked pagecache page for the
856 The filesystem must take care of unlocking the page and
867 system does not go through the filesystem but instead uses bmap
898 filesystem explicitly requesting it as nfs and 9fs do (when they
900 invalidate_inode_pages2(). If the filesystem makes such a call,
951 problems. This callback allows a filesystem to indicate to the
1053 filesystem supports concurrent dir iterators
1146 filesystem in which the inode resides. When opening a device node
1149 driver information. These support routines replace the filesystem file
1152 in the filesystem eventually ends up calling the device driver open()
1163 This describes how a filesystem can overload the standard dentry
1165 individual filesystem implementations. Device drivers have no business
1200 LOOKUP_RCU). If in rcu-walk mode, the filesystem must
1247 and inodes won't disappear, neither will our sb or filesystem
1320 called to allow the filesystem to manage the transition from a
1359 There are a number of functions defined which permit a filesystem to
1412 On mount and remount the filesystem is passed a string containing a
1427 If a filesystem accepts mount options, it must define show_options() to