| /linux/fs/hpfs/ |
| H A D | super.c | 506 struct hpfs_super_block *superblock; in hpfs_fill_super() local 529 if (!(superblock = hpfs_map_sector(s, 16, &bh1, 1))) goto bail2; in hpfs_fill_super() 534 ||*/ le32_to_cpu(superblock->magic) != SB_MAGIC in hpfs_fill_super() 542 if (!sb_rdonly(s) && superblock->funcversion != 2 && superblock->funcversion != 3) { in hpfs_fill_super() 544 (int)superblock->version, (int)superblock->funcversion); in hpfs_fill_super() 558 sbi->sb_root = le32_to_cpu(superblock->root); in hpfs_fill_super() 559 sbi->sb_fs_size = le32_to_cpu(superblock->n_sectors); in hpfs_fill_super() 560 sbi->sb_bitmaps = le32_to_cpu(superblock->bitmaps); in hpfs_fill_super() 561 sbi->sb_dirband_start = le32_to_cpu(superblock->dir_band_start); in hpfs_fill_super() 562 sbi->sb_dirband_size = le32_to_cpu(superblock->n_dir_band); in hpfs_fill_super() [all …]
|
| /linux/Documentation/filesystems/ |
| H A 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 …]
|
| H A 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 115 superblock thereof). This is filled in by the ->get_tree() op. If this 126 mount superblock on an automount. 153 A place for the LSMs to hang their security data for the superblock. The 160 The proposed s_fs_info for a new superblock, set in the superblock by 174 These will be bitwise-OR'd with s->s_iflags when a superblock is created. 184 FS_CONTEXT_FOR_MOUNT, New superblock for explicit mount 198 and attach it to the superblock (or whatever), provided it clears the pointer 279 Called to get or create the mountable root and superblock, using the [all …]
|
| H A D | porting.rst | 135 new file_system_type method - kill_sb(superblock). If you are converting 208 just takes the superblock and inode number as arguments and does the 834 in ->destroy_inode()) is *NOT* ordered wrt superblock destruction; 835 as the matter of fact, the superblock and all associated structures 961 suitable superblock to reuse based on the block device pointer. 963 The new logic tries to find a suitable superblock first based on the device 970 In the old logic concurrent mounters would find the superblock on the list of 972 would hold s_umount they would wait until the superblock became either born or 983 The holder of a block device is now the superblock. 987 superblock without matching on the device pointer stored in the superblock. [all …]
|
| H A D | ext2.rst | 17 Most defaults are determined by the filesystem superblock, and can be 52 sb=n Use alternate superblock at this location. 98 descriptor table stored in the block(s) immediately after the superblock. 112 The superblock contains all the information about the configuration of 113 the filing system. The primary copy of the superblock is stored at an 116 the superblock are stored in block groups throughout the filesystem. 122 superblock feature). The groups chosen are 0, 1 and powers of 3, 5 and 7. 124 The information in the superblock contains fields such as the total 135 All fields in the superblock (as in all other ext2 structures) are stored 225 filesystems. The superblock of the ext2 filesystem contains several [all …]
|
| /linux/security/landlock/ |
| H A D | fs.h | 100 * @inode_refs: Number of pending inodes (from this superblock) that 120 landlock_superblock(const struct super_block *const superblock) 122 return superblock->s_security + landlock_blob_sizes.lbs_superblock; 92 landlock_superblock(const struct super_block * const superblock) landlock_superblock() argument
|
| /linux/Documentation/filesystems/ext4/ |
| H A 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.
|
| H A 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 37 RO_COMPAT_ORPHAN_PRESENT feature in the superblock to indicate there may
|
| H A D | special_inodes.rst | 37 …st 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:
|
| H A 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. 274 - Checksum of the entire superblock, with this field set to zero. 560 the superblock advertises 64-bit block number support, or 4 bytes
|
| H A D | group_descr.rst | 15 group, the only data structures with fixed locations are the superblock 33 the size is stored in the superblock.
|
| H A D | bigalloc.rst | 26 stored in the s_log_cluster_size field in the superblock); from then
|
| /linux/scripts/gdb/linux/ |
| H A D | proc.py | 192 superblock = mnt['mnt']['mnt_sb'] 193 fstype = superblock['s_type']['name'].string() 194 s_flags = int(superblock['s_flags']) 199 mnt.format_string(), superblock.format_string(), devname,
|
| /linux/Documentation/ABI/testing/ |
| H A 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/fs/nilfs2/ |
| H A D | sysfs.h | 77 NILFS_DEV_ATTR_STRUCT(superblock); 139 NILFS_RO_ATTR(superblock, name) 141 NILFS_RW_ATTR(superblock, name)
|
| H A D | sysfs.c | 826 NILFS_DEV_INT_GROUP_OPS(superblock, dev); 827 NILFS_DEV_INT_GROUP_TYPE(superblock, dev); 828 NILFS_DEV_INT_GROUP_FNS(superblock, dev);
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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 52 1. overwrite the superblock with zeroes 56 4. read the "provided_data_sectors" value from the superblock 108 superblock is used. 113 the superblock is used. 203 - the superblock is protected by journal_mac 204 - a 16-byte salt stored in the superblock is mixed to the mac, so 243 * superblock (4kiB) 273 * integrity tag (the size is specified in the superblock) [all …]
|
| /linux/Documentation/networking/ |
| H A 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/drivers/md/persistent-data/ |
| H A D | dm-space-map-metadata.h | 36 dm_block_t superblock);
|
| H A D | dm-transaction-manager.h | 52 int dm_tm_commit(struct dm_transaction_manager *tm, struct dm_block *superblock);
|
| H A D | dm-space-map-metadata.c | 787 dm_block_t superblock) in dm_sm_metadata_create() argument 792 smm->begin = superblock + 1; in dm_sm_metadata_create() 814 r = add_bop(smm, BOP_INC, superblock, smm->begin); in dm_sm_metadata_create()
|
| /linux/fs/cramfs/ |
| H A 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/security/smack/ |
| H A D | smack.h | 377 const struct super_block *superblock) in smack_superblock() argument 379 return superblock->s_security + smack_blob_sizes.lbs_superblock; in smack_superblock()
|
| /linux/fs/befs/ |
| H A 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/fs/freevxfs/ |
| H A D | Kconfig | 12 data endianness and/or superblock offset. The vxfs module has been
|