| /Linux-v5.15/fs/hpfs/ |
| D | super.c | 541 struct hpfs_super_block *superblock; in hpfs_fill_super() local
590 if (!(superblock = hpfs_map_sector(s, 16, &bh1, 1))) goto bail2; in hpfs_fill_super()
595 ||*/ le32_to_cpu(superblock->magic) != SB_MAGIC in hpfs_fill_super()
603 if (!sb_rdonly(s) && superblock->funcversion != 2 && superblock->funcversion != 3) { in hpfs_fill_super()
605 (int)superblock->version, (int)superblock->funcversion); in hpfs_fill_super()
619 sbi->sb_root = le32_to_cpu(superblock->root); in hpfs_fill_super()
620 sbi->sb_fs_size = le32_to_cpu(superblock->n_sectors); in hpfs_fill_super()
621 sbi->sb_bitmaps = le32_to_cpu(superblock->bitmaps); in hpfs_fill_super()
622 sbi->sb_dirband_start = le32_to_cpu(superblock->dir_band_start); in hpfs_fill_super()
623 sbi->sb_dirband_size = le32_to_cpu(superblock->n_dir_band); in hpfs_fill_super()
[all …]
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | qnx6.rst | 41 The superblock contains all global information about the filesystem.
43 That serial number is used to identify the "active" superblock.
45 serial of the new master superblock is increased (old superblock serial + 1)
51 inactive superblock.
53 Each superblock holds a set of root inodes for the different filesystem
72 The Audi MMI 3G first superblock directly starts at byte 0.
74 Second superblock position can either be calculated from the superblock
79 0x1000 is the size reserved for each superblock - regardless of the
98 used. (scheme is the same as the one used for the superblock root nodes)
122 starting with the superblock longfilename root node pointers.
[all …]
|
| D | mount_api.rst | 39 (4) Get or create a superblock and mountable root.
64 The creation and reconfiguration of a superblock is governed by a filesystem
116 superblock thereof). This is filled in by the ->get_tree() op. If this
127 mount superblock on an automount.
154 A place for the LSMs to hang their security data for the superblock. The
161 The proposed s_fs_info for a new superblock, set in the superblock by
175 These will be bitwise-OR'd with s->s_iflags when a superblock is created.
185 FS_CONTEXT_FOR_MOUNT, New superblock for explicit mount
199 and attach it to the superblock (or whatever), provided it clears the pointer
280 Called to get or create the mountable root and superblock, using the
[all …]
|
| D | ext2.rst | 17 Most defaults are determined by the filesystem superblock, and can be
52 sb=n Use alternate superblock at this location.
100 descriptor table stored in the block(s) immediately after the superblock.
114 The superblock contains all the information about the configuration of
115 the filing system. The primary copy of the superblock is stored at an
118 the superblock are stored in block groups throughout the filesystem.
124 superblock feature). The groups chosen are 0, 1 and powers of 3, 5 and 7.
126 The information in the superblock contains fields such as the total
137 All fields in the superblock (as in all other ext2 structures) are stored
227 filesystems. The superblock of the ext2 filesystem contains several
[all …]
|
| /Linux-v5.15/security/landlock/ |
| D | fs.h | 60 const struct super_block *const superblock) in landlock_superblock() argument
62 return superblock->s_security + landlock_blob_sizes.lbs_superblock; in landlock_superblock()
|
| /Linux-v5.15/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 32 The superblock will start at offset 1024 bytes, whichever block that
34 1024, then block 0 is marked in use and the superblock goes in block 1.
37 The ext4 driver primarily works with the superblock and the group
39 superblock and group descriptors are written to some of the block groups
71 superblock, group descriptors, data block bitmaps for groups 0-3, inode
75 large files to be continuous on disk. Backup copies of the superblock
103 the superblock is followed by a variable-length set of block group
104 descriptors. Instead, the superblock and a single block group descriptor
113 the field s\_first\_meta\_bg in the superblock will indicate the first
|
| D | checksums.rst | 8 The desired checksum algorithm is indicated in the superblock, though as
27 of checksum. The checksum function is whatever the superblock describes
39 - The entire superblock up to the checksum field. The UUID lives inside
40 the superblock.
|
| D | orphan.rst | 15 superblock contains the inode number of the last orphan inode (s\_last\_orphan
21 (referenced from the superblock through s\_orphan_file_inum) with several
47 RO\_COMPAT\_ORPHAN\_PRESENT feature in the superblock to indicate there may
|
| D | super.rst | 6 The superblock records various information about the enclosing
11 superblock and group descriptors are kept only in the groups whose group
15 The superblock checksum is calculated against the superblock structure,
18 The ext4 superblock is laid out as follows in
156 - Block group # of this superblock.
218 - UUID of journal superblock
308 MMP is a mechanism to record in the superblock which host and device
420 - Block groups containing superblock backups (if sparse\_super2)
495 The superblock state is some combination of the following:
512 The superblock error policy is one of the following:
[all …]
|
| D | special_inodes.rst | 37 … non-reserved inode. Usually this is the lost+found directory. See s\_first\_ino in the superblock.
41 hierarchy. These are generally reference from the superblock. They are:
|
| D | journal.rst | 43 journal inode are replicated in the ext4 superblock. The journal itself
86 The journal superblock will be in the next full block after the
87 superblock.
150 - Journal superblock, v1.
152 - Journal superblock, v2.
164 The journal superblock is recorded as ``struct journal_superblock_s``,
182 - Common header identifying this as a superblock.
215 - The remaining fields are only valid in a v2 superblock.
269 - Checksum of the entire superblock, with this field set to zero.
555 the superblock advertises 64-bit block number support, or 4 bytes
|
| D | bitmaps.rst | 26 descriptor points to the start of the table, and the superblock records
|
| /Linux-v5.15/scripts/gdb/linux/ |
| D | proc.py | 190 superblock = vfs['mnt']['mnt_sb']
191 fstype = superblock['s_type']['name'].string()
192 s_flags = int(superblock['s_flags'])
197 vfs.format_string(), superblock.format_string(), devname,
|
| /Linux-v5.15/fs/nilfs2/ |
| D | sysfs.h | 77 NILFS_DEV_ATTR_STRUCT(superblock);
139 NILFS_RO_ATTR(superblock, name)
141 NILFS_RW_ATTR(superblock, name)
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-fs-nilfs2 | 60 What: /sys/fs/nilfs2/<device>/superblock/sb_write_time
67 What: /sys/fs/nilfs2/<device>/superblock/sb_write_time_secs
73 What: /sys/fs/nilfs2/<device>/superblock/sb_write_count
79 What: /sys/fs/nilfs2/<device>/superblock/sb_update_frequency
83 Show/Set interval of periodical update of superblock
86 What: /sys/fs/nilfs2/<device>/superblock/README
90 Describe attributes of /sys/fs/nilfs2/<device>/superblock
|
| /Linux-v5.15/Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 37 the device. But it will only format the device if the superblock contains
38 zeroes. If the superblock is neither valid nor zeroed, the dm-integrity
43 1. overwrite the superblock with zeroes
47 4. read the "provided_data_sectors" value from the superblock
94 superblock is used.
99 the superblock is used.
194 - the superblock is protected by journal_mac
195 - a 16-byte salt stored in the superblock is mixed to the mac, so
228 * superblock (4kiB)
258 * integrity tag (the size is specified in the superblock)
[all …]
|
| /Linux-v5.15/security/selinux/include/ |
| D | objsec.h | 192 const struct super_block *superblock) in selinux_superblock() argument
194 return superblock->s_security + selinux_blob_sizes.lbs_superblock; in selinux_superblock()
|
| /Linux-v5.15/drivers/md/persistent-data/ |
| D | dm-space-map-metadata.h | 35 dm_block_t superblock);
|
| D | dm-transaction-manager.h | 51 int dm_tm_commit(struct dm_transaction_manager *tm, struct dm_block *superblock);
|
| /Linux-v5.15/Documentation/networking/ |
| D | sysfs-tagging.rst | 29 Each sysfs superblock's kernfs_super_info contains an array
31 kobj_nstype first mounts sysfs, a new superblock is created. It
|
| /Linux-v5.15/fs/btrfs/ |
| D | check-integrity.c | 2071 struct btrfsic_block *const superblock, in btrfsic_process_written_superblock() argument
2077 superblock->generation = btrfs_super_generation(super_hdr); in btrfsic_process_written_superblock()
2078 if (!(superblock->generation > state->max_superblock_generation || in btrfsic_process_written_superblock()
2082 superblock->logical_bytenr, in btrfsic_process_written_superblock()
2083 superblock->dev_state->name, in btrfsic_process_written_superblock()
2084 superblock->dev_bytenr, superblock->mirror_num, in btrfsic_process_written_superblock()
2090 superblock->logical_bytenr, in btrfsic_process_written_superblock()
2091 superblock->dev_state->name, in btrfsic_process_written_superblock()
2092 superblock->dev_bytenr, superblock->mirror_num, in btrfsic_process_written_superblock()
2098 state->latest_superblock = superblock; in btrfsic_process_written_superblock()
[all …]
|
| /Linux-v5.15/fs/cramfs/ |
| D | README | 13 <superblock>
17 <superblock>: struct cramfs_super (see cramfs_fs.h).
120 The superblock ought to indicate the block size that the fs was
149 data, only the superblock, inodes and block pointers.
|
| /Linux-v5.15/security/smack/ |
| D | smack.h | 361 const struct super_block *superblock) in smack_superblock() argument
363 return superblock->s_security + smack_blob_sizes.lbs_superblock; in smack_superblock()
|
| /Linux-v5.15/fs/befs/ |
| D | ChangeLog | 79 * Abbandoned silly checks for a NULL superblock pointer in debug.c. [WD]
167 superblock type, rather than struct super_block. This is for
178 * Added functions to get the private superblock and inode structures from
244 * Fixed a problem with reading the superblock on devices with large sector
375 very end of befs_read_super(), after we are done with the disk superblock.
396 * Removed superblock locking calls in befs_read_super(). In 2.4, the VFS
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | md.rst | 84 superblock can be autodetected and run at boot time.
118 The md driver can support a variety of different superblock formats.
119 Currently, it supports superblock formats ``0.90.0`` and the ``md-1`` format
122 The kernel will autodetect which format superblock is being used.
125 reasons - it is the original superblock format.
128 General Rules - apply for all superblock formats
146 version number. The major version number selects which superblock
149 superblock.
158 appropriate superblock written to them, and then be passed in with
165 Specific Rules that apply to format-0 super block arrays, and arrays with no superblock (non-persis…
[all …]
|
