Lines Matching refs:filesystem
17 the software layer in the kernel that provides the filesystem interface
19 kernel which allows different filesystem implementations to coexist.
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
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. See Documentation/filesystems/mount_api.rst
108 This describes the filesystem. The following
135 the name of the filesystem type, such as "ext2", "iso9660",
143 filesystem-specific data.
146 Pointer to the array of filesystem parameters descriptors
151 the method to call when an instance of this filesystem should be
163 for internal VFS use: hlist of filesystem instances (superblocks)
171 A superblock object represents a mounted filesystem.
178 filesystem. The following members are defined:
258 This method should be either NULL (normal UNIX filesystem
286 down_write(&sb->s_umount). If filesystem implements it and wants
291 called when VFS is locking a filesystem and forcing it into a
296 called when VFS is unlocking a filesystem and making it writable
300 called when VFS is unlocking a filesystem and making it writable
304 called when the VFS needs to get filesystem statistics.
307 called when the VFS is unmounting a filesystem.
321 the mount root dentry path relative to the filesystem root.
325 filesystem-specific mount statistics.
328 called by the VFS to read from filesystem quota file.
331 called by the VFS to write to filesystem quota file.
338 called by the sb cache shrinking function for the filesystem to
343 called by the sb cache shrinking function for the filesystem to
345 Optional, but any filesystem implementing this method needs to
349 We can't do anything with any errors that the filesystem might
398 When none of the xattr handlers of a filesystem match the specified
399 attribute name or when a filesystem doesn't support extended attributes,
406 An inode object represents an object within the filesystem.
412 This describes how the VFS can manipulate an inode in your filesystem.
496 accessible by another path (e.g. with a network filesystem)
503 For example, if an NFS filesystem is mounted twice the new directory
528 The filesystem must return -EINVAL for any unsupported or
553 If the filesystem stores the symlink target in ->i_link, the
568 filesystem.
571 rcu-walk mode, the filesystem must check the permission without
602 method the filesystem can look up, possibly create and open the
605 symlink, device, or just something filesystem won't do atomic
634 filesystem must define this operation to use
749 cache in your filesystem. The following members are defined:
792 be marked uptodate. The filesystem should unlock the folio
794 The filesystem does not need to modify the refcount on the folio;
805 If the filesystem cannot perform the read at this time, it can
841 filesystem should attempt to read all sync pages but may decide
849 Called by the generic buffered write code to ask the filesystem
858 The filesystem must return the locked pagecache folio for the
876 The filesystem must take care of unlocking the folio,
887 system does not go through the filesystem but instead uses bmap
906 filesystem that the folio is about to be freed. ->release_folio
917 filesystem explicitly requesting it as nfs and 9p do (when they
919 invalidate_inode_pages2(). If the filesystem makes such a call,
962 problems. This callback allows a filesystem to indicate to the
1175 filesystem in which the inode resides. When opening a device node
1178 driver information. These support routines replace the filesystem file
1181 in the filesystem eventually ends up calling the device driver open()
1192 This describes how a filesystem can overload the standard dentry
1194 individual filesystem implementations. Device drivers have no business
1232 LOOKUP_RCU). If in rcu-walk mode, the filesystem must
1279 and inodes won't disappear, neither will our sb or filesystem
1350 called to allow the filesystem to manage the transition from a
1385 and d_exchange() calls from the outside of filesystem methods;
1406 There are a number of functions defined which permit a filesystem to
1459 On mount and remount the filesystem is passed a string containing a
1474 If a filesystem accepts mount options, it must define show_options() to