/fs/cramfs/ |
D | README | 7 a given directory are contiguous, as this is used by readdir). 9 All data is currently in host-endian format; neither mkcramfs nor the 22 Filename. Not generally null-terminated, but it is 25 The order of inode traversal is described as "width-first" (not to be 47 *end* of the i'th <block> (i.e. one past the last byte, which is the 48 same as the start of the (i+1)'th <block> if there is one). The first 52 The order of <file_data>'s is a depth-first descent of the directory 57 <block>: The i'th <block> is the output of zlib's compress function 87 (Block size in cramfs refers to the size of input data that is 98 turn is defined as PAGE_SIZE (which can be as large as 32KB on arm). [all …]
|
D | Kconfig | 7 System). CramFs is designed to be a simple, small, and compressed 8 file system for ROM based embedded systems. CramFs is read-only, 19 This filesystem is obsoleted by SquashFS, which is much better
|
/fs/jffs2/ |
D | README.Locking | 6 JFFS2. It is not expected to remain perfectly up to date, but ought to 13 The alloc_sem is a per-filesystem mutex, used primarily to ensure 14 contiguous allocation of space on the medium. It is automatically 24 which they belong. This is for the benefit of NAND flash - adding new 33 the alloc_sem is also used to protect the wbuf-related members of the 35 if the wbuf is currently holding any data is permitted, though. 43 This is the JFFS2-internal equivalent of the inode mutex i->i_sem. 48 The reason that the i_sem itself isn't used for this purpose is to 59 mutex, which is obtained by the garbage collection code and also 74 This is used to serialise access to the eraseblock lists, to the [all …]
|
/fs/ntfs/ |
D | Kconfig | 5 NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. 7 Saying Y or M here enables read support. There is partial, but 15 This is a rewrite from scratch of Linux NTFS support and replaced 17 the Linux 2.4 kernel series is separately available as a patch 27 Linux on your computer it is safe to say N. 39 to insmod when loading the ntfs module. Once the driver is active, 57 The only supported operation is overwriting existing files, without 59 renaming is possible. Note only non-resident files can be written to 65 damaged someones data so we assume it is perfectly safe to use. 67 Note: While write support is safe in this version (a rewrite from [all …]
|
/fs/ext4/ |
D | inline.c | 133 struct ext4_xattr_ibody_find is = { in ext4_find_inline_data_nolock() local 145 error = ext4_get_inode_loc(inode, &is.iloc); in ext4_find_inline_data_nolock() 149 error = ext4_xattr_ibody_find(inode, &i, &is); in ext4_find_inline_data_nolock() 153 if (!is.s.not_found) { in ext4_find_inline_data_nolock() 154 EXT4_I(inode)->i_inline_off = (u16)((void *)is.s.here - in ext4_find_inline_data_nolock() 155 (void *)ext4_raw_inode(&is.iloc)); in ext4_find_inline_data_nolock() 157 le32_to_cpu(is.s.here->e_value_size); in ext4_find_inline_data_nolock() 161 brelse(is.iloc.bh); in ext4_find_inline_data_nolock() 252 struct ext4_xattr_ibody_find is = { in ext4_create_inline_data() local 260 error = ext4_get_inode_loc(inode, &is.iloc); in ext4_create_inline_data() [all …]
|
D | xattr.c | 1032 struct ext4_xattr_ibody_find *is) in ext4_xattr_ibody_find() argument 1040 raw_inode = ext4_raw_inode(&is->iloc); in ext4_xattr_ibody_find() 1042 is->s.base = is->s.first = IFIRST(header); in ext4_xattr_ibody_find() 1043 is->s.here = is->s.first; in ext4_xattr_ibody_find() 1044 is->s.end = (void *)raw_inode + EXT4_SB(inode->i_sb)->s_inode_size; in ext4_xattr_ibody_find() 1046 error = xattr_check_inode(inode, header, is->s.end); in ext4_xattr_ibody_find() 1050 error = ext4_xattr_find_entry(&is->s.here, i->name_index, in ext4_xattr_ibody_find() 1051 i->name, is->s.end - in ext4_xattr_ibody_find() 1052 (void *)is->s.base, 0); in ext4_xattr_ibody_find() 1055 is->s.not_found = error; in ext4_xattr_ibody_find() [all …]
|
D | Kconfig | 13 This config option is here only for backward compatibility. ext3 14 filesystem is now handled by the ext4 driver. 22 This config option is here only for backward compatibility. ext3 23 filesystem is now handled by the ext4 driver. 30 This config option is here only for backward compatibility. ext3 31 filesystem is now handled by the ext4 driver. 41 This is the next generation of the ext3 filesystem. 44 the on-disk format of ext4 is not forwards compatible with 45 ext3; it is based on extent maps and it supports 48-bit 116 feature is similar to ecryptfs, but it is more memory
|
/fs/btrfs/ |
D | Kconfig | 16 Btrfs is a general purpose copy-on-write filesystem with extents, 20 The filesystem disk format is no longer unstable, and it's not 22 is a format change, file systems with a unchanged format will 51 writes of the super block). The goal is to verify that the 52 state of the filesystem on disk is always consistent, i.e., 53 after a power-loss or kernel panic event the filesystem is 56 If the integrity check tool is included and activated in 57 the mount options, plenty of kernel memory is used, and 59 functionality is not intended for normal use. 70 code to make sure it is acting as it should. These are mostly [all …]
|
/fs/affs/ |
D | Changes | 11 in readdir()) gives compiler warnings but is 24 - When a file is truncated to a size that is not 26 last allocated block is not cleared. Well, 113 partially used last block when a file is truncated. 114 It also marks the inode dirty now (which is not 138 - One set of dentry callbacks is enough. (BH) 144 - The original blocksize of the device is 145 restored when the fs is unmounted. (BH) 209 is that unlink(), rename() and rmdir() have to 210 be smart about them, but the result is worth the [all …]
|
/fs/ubifs/ |
D | Kconfig | 12 UBIFS is a file system for flash devices which works on top of UBI. 29 LZO compressor is generally faster than zlib but compresses worse. 37 Zlib compresses better than LZO but it is slower. Say 'Y' if unsure. 45 increased flash wear. This option adds atime support and it is disabled by default 49 so be careful. How often atime is updated depends on the selected strategy: 50 strictatime is the "heavy", relatime is "lighter", etc.
|
/fs/xfs/ |
D | Kconfig | 8 XFS is a high performance journaling filesystem which originated 9 on the SGI IRIX platform. It is completely multi-threaded, can 11 variable block sizes, is extent based, and makes extensive use of 16 for complete details. This implementation is on-disk compatible 21 system of your root partition is compiled as a module, you'll need 33 quota is also compatible with the IRIX version of XFS, allowing a 60 which contain a realtime subvolume. The realtime subvolume is a 61 separate area of disk space where only file data is stored. It was 63 for media streaming applications, but is also useful as a generic 79 conditions that occur that would otherwise be missed. It is much [all …]
|
/fs/befs/ |
D | ChangeLog | 34 This is bad, since 2.4.9 is still the current RedHat kernel. I added 51 finding the first key that is a substring of the string it is searching 63 * Makefile fix for independent module when CONFIG_MODVERSION is set in 96 * Make directory lookup/read use the NLS if an iocharset is provided. [WD] 102 The option is, simply enough, 'debug'. 111 node. This is the cleaner solution to Brent Miszalaski's problem. [WD] 150 * Anton also told me that the blocksize is not allowed to be larger than 151 the page size in linux, which is 4k i386. Oops. Added a test for 153 practically means is that 8k blocksize volumes won't work without a major 167 superblock type, rather than struct super_block. This is for [all …]
|
/fs/reiserfs/ |
D | README | 3 ReiserFS is hereby licensed under the GNU General 17 licensing is governed by the statement in this file, you accept this. 18 It will be a kindness if you identify whether Hans Reiser is allowed 20 under the GPL, because he wants to know if it is okay to do so and put 39 If you have doubts about how to properly do that, or about what is 45 Reiserfs is a file system based on balanced tree algorithms, which is 53 Linux provider put them. There is some disagreement about how useful 54 it is for users to get their fsck and mkreiserfs out of sync with the 55 version of reiserfs that is in their kernel, with many important 58 reiserfs, this is a common source of confusion. Note that some of the [all …]
|
/fs/ocfs2/ |
D | Kconfig | 10 OCFS2 is a general purpose extent based shared disk cluster file 33 O2CB is limited to maintaining a cluster for OCFS2 file systems. 36 It is always safe to say Y here, as the clustering method is 48 It is safe to say Y, as the clustering method is run-time 75 this option for debugging only as it is likely to decrease
|
/fs/configfs/ |
D | Kconfig | 5 configfs is a RAM-based filesystem that provides the converse 6 of sysfs's functionality. Where sysfs is a filesystem-based 7 view of kernel objects, configfs is a filesystem-based manager 11 same system. One is not a replacement for the other.
|
/fs/ncpfs/ |
D | Kconfig | 8 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is 9 used by Novell NetWare clients to talk to file servers. It is to 10 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you 20 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. 63 case insensitive, and case in names is preserved. Say Y. You can 75 This is only a cosmetic option since the OS2/LONG namespace is case 76 insensitive. The only major reason for this option is backward 106 To use the new attributes, it is recommended to use the flags
|
/fs/isofs/ |
D | Kconfig | 4 This is the standard file system used on CD-ROMs. It was previously 5 known as "High Sierra File System" and is called "hsfs" on other 22 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system 23 which allows for long filenames in unicode format (unicode is the 34 This is a Linux-specific extension to RockRidge which lets you store 36 decompressed when the CD-ROM is accessed. See
|
/fs/gfs2/ |
D | Kconfig | 11 that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads 14 filesystem consistency is maintained. One of the nifty features of 15 GFS is perfect consistency -- changes made to the filesystem on one 22 The "nolock" lock module is now built in to GFS2 by default. If 33 interface between GFS2 and the DLM, which is required to use GFS2
|
/fs/freevxfs/ |
D | Kconfig | 5 FreeVxFS is a file system driver that support the VERITAS VxFS(TM) 6 file system format. VERITAS VxFS(TM) is the standard file system 9 Currently only readonly access is supported. 12 fstab(5) is 'vxfs' as it describes the file system format, not
|
/fs/cifs/ |
D | Kconfig | 15 This is the client VFS module for the Common Internet File System 16 (CIFS) protocol which is the successor to the Server Message Block 18 PC operating systems. The CIFS protocol is fully supported by 22 support for OS/2 and Windows ME and similar servers is provided as 67 SMB protocol but LANMAN based authentication is needed to 76 is enabled in the kernel build, LANMAN authentication will not be 80 option on the mount command. This support is disabled by 94 secure Kerberos authentication is required). If unsure, say N. 107 (used by some filesystems to store ACLs) is not supported at 129 is handed over to the application/caller. See the man [all …]
|
/fs/udf/ |
D | Kconfig | 5 This is a file system used on some CD-ROMs and DVDs. Since the 6 file system is supported by multiple operating systems and is more 7 compatible with standard unix file systems, it is also suitable for
|
/fs/notify/fanotify/ |
D | Kconfig | 7 Say Y here to enable fanotify support. fanotify is a file access 20 Say Y here is you want fanotify listeners to be able to make permissions 21 decisions concerning filesystem events. This is used by some fanotify 23 use those files. This is used by some anti-malware vendors and by some
|
/fs/jbd2/ |
D | Kconfig | 7 This is a generic journaling layer for block devices that support 8 both 32-bit and 64-bit block numbers. It is currently used by 27 allows you to enable debugging output while the system is running, 32 with "echo N > /sys/module/jbd2/parameters/jbd2_debug", where N is a 34 output is generated. To turn debugging off again, do
|
/fs/squashfs/ |
D | Kconfig | 6 Read-Only File System). Squashfs is a highly compressed read-only 15 Squashfs is intended for general read-only filesystem use, for 17 embedded systems where low overhead is needed. Further information 68 decompression is load-balanced across the cores. 88 ZLIB compression is the standard compression used by Squashfs 101 compressed with LZ4 compression. LZ4 compression is mainly 105 LZ4 is not the standard compression used in Squashfs and so most 116 compressed with LZO compression. LZO compression is mainly 120 LZO is not the standard compression used in Squashfs and so most 135 XZ is not the standard compression used in Squashfs and so most [all …]
|
/fs/autofs4/ |
D | Kconfig | 4 The automounter is a tool to automatically mount remote file systems 5 on demand. This implementation is partially kernel-based to reduce 6 overhead in the already-mounted case; this is unlike the BSD 7 automounter (amd), which is a pure user space daemon.
|