| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 10 Userspace filesystem:
11 A filesystem in which data and metadata are provided by an ordinary
12 userspace process. The filesystem can be accessed normally through
15 Filesystem daemon:
16 The process(es) providing the data and metadata of the filesystem.
19 A userspace filesystem mounted by a non-privileged (non-root) user.
20 The filesystem daemon is running with the privileges of the mounting
24 Filesystem connection:
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
[all …]
|
| H A D | fuse-passthrough.rst | 10 FUSE (Filesystem in Userspace) passthrough is a feature designed to improve the
18 the backing file on a lower filesystem) with the FUSE kernel module. The kernel
33 1. The FUSE filesystem must be compiled with ``CONFIG_FUSE_PASSTHROUGH``
79 file is still open by the system on behalf of the FUSE filesystem. This
98 Filesystem Stacking and Shutdown Loops
102 filesystem stacking scenarios if unprivileged users could set up passthrough.
103 A FUSE passthrough filesystem might use a backing file that resides:
105 * On the *same* FUSE filesystem.
106 * On another filesystem (like OverlayFS) which itself might have an upper or
107 lower layer that is a FUSE filesystem.
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 6 Most filesystem developers will have encountered idmappings. They are used when
8 for permission checking. This document is aimed at filesystem developers that
157 outside of the filesystem context. This is best left to an explanation of user
173 ownership of a file is read from disk by a filesystem, the userspace id is
177 For instance, consider a file that is stored on disk by a filesystem as being
180 - If a filesystem were to be mounted in the initial user namespaces (as most
186 - If a filesystem were to be mounted with an idmapping of ``u0:k10000:r10000``
233 into a kernel id according to the idmapping associated with the filesystem.
234 Let's assume the filesystem was mounted with an idmapping of
241 according to the filesystem's idmapping as this would give the wrong owner if
[all …]
|
| H A D | directory-locking.rst | 7 kinds of locks - per-inode (->i_rwsem) and per-filesystem
55 * lock the filesystem
96 and fail the lookup if it is. Then we try to lock the filesystem and the
101 Note that splicing does *not* involve any modification of the filesystem;
104 filesystem lock prevents any changes of tree topology, other than having a
107 the filesystem lock, their relationship will remain unchanged until
114 Multiple-filesystem stuff
118 another filesystem; it may be ecryptfs doing operation in the underlying
119 filesystem, overlayfs doing something to the layers, network filesystem
122 directory operation on this filesystem might involve directory operations
[all …]
|
| H A D | qnx6.rst | 4 The QNX6 Filesystem
13 mmi_fs Mount filesystem as used for example by Audi MMI 3G system
32 size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
41 The superblock contains all global information about the filesystem.
50 (or period) and building up a new (stable) filesystem structure under the
53 Each superblock holds a set of root inodes for the different filesystem
75 information (total number of filesystem blocks) or by taking the highest
80 blocksize of the filesystem.
85 Each object in the filesystem is represented by an inode. (index node)
86 The inode structure contains pointers to the filesystem blocks which contain
[all …]
|
| H A D | hfs.rst | 4 Macintosh HFS Filesystem for Linux
8 .. Note:: This filesystem doesn't have a maintainer.
11 HFS stands for ``Hierarchical File System`` and is the filesystem used
14 MacOS 8.1 and newer support a filesystem called HFS+ that's similar to
15 HFS but is extended in various areas. Use the hfsplus filesystem driver
22 When mounting an HFS filesystem, the following options are accepted:
37 Select the CDROM session to mount as HFS filesystem. Defaults to
54 HFS is not a UNIX filesystem, thus it does not have the usual features you'd
70 * Copying files to a different filesystem will loose those attributes
78 hformat that can be used to create HFS filesystem. See
|
| H A D | befs.rst | 4 BeOS filesystem for Linux
36 This filesystem doesn't have a maintainer.
40 This module implements the native filesystem of BeOS http://www.beincorporated.com/
46 Be, Inc said, "BeOS Filesystem is officially called BFS, not BeFS".
47 But Unixware Boot Filesystem is called bfs, too. And they are already in
49 filesystem is called befs.
81 filesystem (experimental)", or something like that. Enable that option
93 To use the BeOS filesystem, use filesystem type 'befs'.
123 Dominic Giampalo ... Writing "Practical file system design with Be filesystem"
|
| H A D | vfat.rst | 8 To use the vfat filesystem, use the filesystem type 'vfat'. i.e.::
20 Set the owner of all files on this filesystem.
24 Set the group of all files on this filesystem.
52 filesystem doesn't have uid/gid on disk, so normal
58 characters on FAT filesystem.
76 UTF-8 is the filesystem safe version of Unicode that
78 for the filesystem with this option.
90 illegal on the vfat filesystem. The escape sequence
154 not the time zone used by the filesystem. Note that this
172 If set, the filesystem will try to flush to disk more
[all …]
|
| H A D | romfs.rst | 7 This is a quite dumb, read only filesystem, mainly for initial RAM
9 modules linked at boot time. Using this filesystem, you get a very
17 code). Under the same conditions, the msdos filesystem would need
31 which has only this filesystem linked in, and then can load any module
37 maybe even affs filesystem until you really know that you need it.
40 drivers (and possibly the SCSI drivers), and the ISO 9660 filesystem
58 The layout of the filesystem is the following::
80 The first eight bytes identify the filesystem, even for the casual
82 bytes accessible from the start of this filesystem. The 4th longword
85 as in the AFFS filesystem, namely a simple sum of the longwords
[all …]
|
| /linux/fs/ext4/ |
| H A D | Kconfig | 3 tristate "The Extended 4 (ext4) filesystem"
11 This is the next generation of the ext3 filesystem.
13 Unlike the change from ext2 filesystem to ext3 filesystem,
16 physical block numbers. The ext4 filesystem also supports delayed
22 The ext4 filesystem supports mounting an ext3 filesystem; while there
25 features in the filesystem using tune2fs, or formatting a new
26 filesystem as an ext4 filesystem initially. Without explicit enabling
27 of ext4 features, the on disk filesystem format stays fully backward
63 labels in the ext4 filesystem.
72 Enables run-time debugging support for the ext4 filesystem.
|
| /linux/fs/xfs/ |
| H A D | Kconfig | 3 tristate "XFS filesystem support"
9 XFS is a high performance journaling filesystem which originated
30 The V4 filesystem format lacks certain features that are supported
37 Administrators and users can detect a V4 filesystem by running
38 xfs_info against a filesystem mountpoint and checking for a string
40 filesystem is a V4 filesystem. If no such string is found, please
55 The ASCII case insensitivity filesystem feature only works correctly
64 Administrators and users can detect such a filesystem by running
65 xfs_info against a filesystem mountpoint and checking for a string
67 filesystem is a case-insensitive filesystem. If no such string is
[all …]
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | design.rst | 20 iomap is a filesystem library for handling common file operations.
25 from the filesystem, but the storage information is not necessarily
52 The target audience for this document are filesystem, storage, and
63 the basis of that unit, the iomap model asks the filesystem for the
66 This strategy improves the filesystem's visibility into the size of the
70 of mapping function calls into the filesystem across a larger amount of
130 * **filesystem mapping lock**: This synchronization primitive is
131 internal to the filesystem and must protect the file mapping data
133 The filesystem author must determine how this coordination should
145 This implies that the filesystem must have already allocated space
[all …]
|
| H A D | porting.rst | 11 Porting Your Filesystem
20 There are several reasons to convert a filesystem to iomap:
24 into the filesystem to return a mapping for only that page.
37 4. Lower maintenance overhead for individual filesystem maintainers.
42 filesystem using iomap.
44 How Do I Convert a Filesystem?
48 ``select FS_IOMAP`` to your filesystem's Kconfig option.
50 variety of your filesystem's supported configurations to build a
64 Next, modify the filesystem's ``get_block(create = false)``
96 w/ DIO enabled in earnest on filesystem.
[all …]
|
| H A D | operations.rst | 31 This means that the filesystem need not know the details of allocating,
37 Unless the filesystem explicitly opts in to buffer heads, they will not
81 This could be used to `set up per-folio filesystem state
89 This could be used to `commit per-folio filesystem state
93 - ``iomap_valid``: The filesystem may not hold locks between
105 Races can also happen if the filesystem allows concurrent writes.
116 To support making the validity decision, the filesystem's
120 If the filesystem bumps the sequence counter every time it modifies
124 the filesystem holds when the mapping is passed back to
204 filesystem.
[all …]
|
| /linux/Documentation/filesystems/caching/ |
| H A D | netfs-api.rst | 4 Network Filesystem Caching API
7 Fscache provides an API by which a network filesystem can make use of local
45 The fscache hierarchy is organised on two levels from a network filesystem's
50 A network filesystem acquires a volume cookie for a volume using a volume key,
58 A filesystem would typically have a volume cookie for each superblock.
60 The filesystem then acquires a cookie for each file within that volume using an
65 filesystem.
67 A filesystem would typically have a cookie for each inode, and would acquire it
70 Once it has a cookie, the filesystem needs to mark the cookie as being in use.
75 A filesystem would typically "use" the cookie in its file open routine and
[all …]
|
| /linux/fs/overlayfs/ |
| H A D | Kconfig | 3 tristate "Overlay filesystem support"
7 An overlay filesystem combines two filesystems - an 'upper' filesystem
8 and a 'lower' filesystem. When a name exists in both filesystems, the
9 object in the 'upper' filesystem is visible while the object in the
10 'lower' filesystem is either hidden or, in the case of directories,
22 "redirect_dir=off" module option or on a filesystem instance basis
53 "index=off" module option or on a filesystem instance basis with the
74 globally with the "nfs_export=off" module option or on a filesystem
100 unused high bits in underlying filesystem inode numbers to map all
120 module option or on a filesystem instance basis with the
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | mmp.rst | 7 filesystem against multiple hosts trying to use the filesystem
8 simultaneously. When a filesystem is opened (for mounting, or fsck,
15 filesystem is active on another machine and the open fails. If the MMP
19 While the filesystem is live, the kernel sets up a timer to re-check the
23 filesystem, and node A remounts the filesystem read-only. If the
57 - Hostname of the node that opened the filesystem.
61 - Block device name of the filesystem.
|
| H A D | orphan.rst | 7 are still alive because they are open. In case of crash the filesystem has to
17 inode (we overload i_dtime inode field for this). However this filesystem
20 (COMPAT_ORPHAN_FILE) is enabled, the filesystem has a special inode
36 When a filesystem with orphan file feature is writeably mounted, we set
39 filesystem, we read the whole orphan file and process all orphan inodes found
40 there as usual. When cleanly unmounting the filesystem we remove the
42 file and also make the filesystem fully compatible with older kernels.
|
| /linux/include/linux/fs/ |
| H A D | super.h | 72 * Decrement number of writers to the filesystem. Wake up possible waiters
73 * wanting to freeze the filesystem.
84 * Decrement number of processes handling write page fault to the filesystem.
85 * Wake up possible waiters wanting to freeze the filesystem.
96 * Decrement fs-internal number of writers to the filesystem. Wake up possible
97 * waiters wanting to freeze the filesystem.
116 * ordering of freeze protection and other filesystem locks. Generally,
150 * ordering of freeze protection and other filesystem locks. It is advised to
166 * This is the third level of protection against filesystem freezing. It is
167 * free for use by a filesystem. The only requirement is that it must rank
[all …]
|
| /linux/fs/fuse/ |
| H A D | Kconfig | 3 tristate "FUSE (Filesystem in Userspace) support"
7 With FUSE it is possible to implement a fully functional filesystem
20 a filesystem based on FUSE, answer Y or M.
33 tristate "Virtio Filesystem"
37 The Virtio Filesystem allows guests to mount file systems from the
44 bool "Virtio Filesystem Direct Host Memory Access support"
54 If you want to allow mounting a Virtio Filesystem with the "dax"
|
| /linux/include/uapi/linux/ |
| H A D | falloc.h | 22 * filesystem block size boundaries, but this boundary may be larger or
23 * smaller depending on the filesystem and/or the configuration of the
24 * filesystem or file.
53 * of the operation. Most will limit operations to filesystem block size
55 * the filesystem and/or the configuration of the filesystem or file.
70 * granularity of the operation. Most will limit operations to filesystem
72 * depending on the filesystem and/or the configuration of the filesystem
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | LoadPin.rst | 6 (modules, firmware, etc) all originate from the same filesystem, with
7 the expectation that such a filesystem is backed by a read-only device
9 and/or unchangeable filesystem to enforce module and firmware loading
18 block device backing the filesystem is not read-only, a sysctl is
20 a mutable filesystem means pinning is mutable too, but having the
21 sysctl allows for easy testing on systems with a mutable filesystem.)
|
| /linux/fs/ |
| H A D | mnt_idmapping.c | 60 * make_vfsuid - map a filesystem kuid according to an idmapping
62 * @fs_userns: the filesystem's idmapping
70 * If initial_idmapping() tells us that the filesystem is not mounted with an
101 * make_vfsgid - map a filesystem kgid according to an idmapping
103 * @fs_userns: the filesystem's idmapping
111 * If initial_idmapping() tells us that the filesystem is not mounted with an
140 * from_vfsuid - map a vfsuid into the filesystem idmapping
142 * @fs_userns: the filesystem's idmapping
145 * Map @vfsuid into the filesystem idmapping. This function has to be used in
148 * Return: @vfsuid mapped into the filesystem idmapping
[all …]
|
| H A D | super.c | 9 * - filesystem drivers list
217 * prune the icache, followed by the filesystem specific caches in super_cache_scan()
247 * rwsem does not protect filesystem operations backing in super_cache_count()
253 * filesystem might be in a state of partial construction and hence it in super_cache_count()
310 * @type: filesystem type superblock should belong to
552 * filesystem is not shut down while we are working on it. It returns
554 * filesystem already got into shutdown, and returns true with the s_umount
614 * Upon calling this function, the filesystem may no longer alter or
704 * @fc: Filesystem context.
717 * (1) the namespace the filesystem context @fc and the extant
[all …]
|
| /linux/fs/vboxsf/ |
| H A D | shfl_hostintf.h | 170 * The user owning the filesystem object (st_uid).
176 * The group the filesystem object is assigned (st_gid).
182 * Number of hard links to this filesystem object (st_nlink).
183 * This field is 1 if the filesystem doesn't support hardlinking or
189 * The device number of the device which this filesystem object resides
195 * The unique identifier (within the filesystem) of this filesystem
228 /** Shared folder filesystem object attributes. */
253 /** Filesystem object information structure. */
430 /** Shared folder filesystem properties. */
433 * The maximum size of a filesystem object name.
[all …]
|