| /linux-3.4.99/fs/hpfs/ |
| D | super.c | 453 struct hpfs_super_block *superblock; in hpfs_fill_super() local
507 if (!(superblock = hpfs_map_sector(s, 16, &bh1, 1))) goto bail2; in hpfs_fill_super()
512 ||*/ le32_to_cpu(superblock->magic) != SB_MAGIC in hpfs_fill_super()
520 superblock->funcversion != 2 && superblock->funcversion != 3) { in hpfs_fill_super()
522 (int)superblock->version, (int)superblock->funcversion); in hpfs_fill_super()
534 sbi->sb_root = le32_to_cpu(superblock->root); in hpfs_fill_super()
535 sbi->sb_fs_size = le32_to_cpu(superblock->n_sectors); in hpfs_fill_super()
536 sbi->sb_bitmaps = le32_to_cpu(superblock->bitmaps); in hpfs_fill_super()
537 sbi->sb_dirband_start = le32_to_cpu(superblock->dir_band_start); in hpfs_fill_super()
538 sbi->sb_dirband_size = le32_to_cpu(superblock->n_dir_band); in hpfs_fill_super()
[all …]
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | qnx6.txt | 35 The superblock contains all global information about the filesystem.
37 That serial number is used to identify the "active" superblock.
39 serial of the new master superblock is increased (old superblock serial + 1)
45 inactive superblock.
47 Each superblock holds a set of root inodes for the different filesystem
64 The Audi MMI 3G first superblock directly starts at byte 0.
65 Second superblock position can either be calculated from the superblock
70 0x1000 is the size reserved for each superblock - regardless of the
88 used. (scheme is the same as the one used for the superblock root nodes)
107 starting with the superblock longfilename root node pointers.
[all …]
|
| D | sysfs-tagging.txt | 26 Each sysfs superblock's sysfs_super_info contains an array void
28 kobj_nstype first mounts sysfs, a new superblock is created. It
|
| D | logfs.txt | 12 Each superblock is 256 Bytes large, with another 3840 Bytes reserved
16 first non-bad block contains a superblock in the first 4096 Bytes and
17 the last non-bad block contains a superblock in the last 4096 Bytes.
19 superblock and the last aligned 4096 Byte-block contains the second
20 superblock.
25 As a result, the superblock does not contain any fields that require
|
| D | ext2.txt | 14 Most defaults are determined by the filesystem superblock, and can be
45 sb=n Use alternate superblock at this location.
90 descriptor table stored in the block(s) immediately after the superblock.
104 The superblock contains all the information about the configuration of
105 the filing system. The primary copy of the superblock is stored at an
108 the superblock are stored in block groups throughout the filesystem.
114 superblock feature). The groups chosen are 0, 1 and powers of 3, 5 and 7.
116 The information in the superblock contains fields such as the total
127 All fields in the superblock (as in all other ext2 structures) are stored
217 filesystems. The superblock of the ext2 filesystem contains several
[all …]
|
| D | Locking | 94 cross-directory ->rename() has (per-superblock) ->s_vfs_rename_sem.
149 the superblock down when we only have dev_t given us by userland to
150 identify the superblock. Everything else (statfs(), fstatfs(), etc.)
151 doesn't hold it when calling ->statfs() - superblock is pinned down
173 ->mount() returns ERR_PTR or the root dentry; its superblock should be locked
175 ->kill_sb() takes a write-locked superblock, does all shutdown work on it,
488 FS recursion means calling ->quota_read() and ->quota_write() from superblock
|
| D | exofs.txt | 123 * The file system control block (AKA on-disk superblock) resides in an object
126 in-memory superblock structure at mount time. This object is created before
145 * Credentials are generated per object (inode and superblock) when they are
|
| D | xfs.txt | 33 removing extended attributes) the on-disk superblock feature
159 restore the value from the superblock. For filesystems that
161 to override the information in the superblock if the underlying
|
| D | vfs.txt | 158 caller. An active reference to its superblock must be grabbed and the
159 superblock must be locked. On failure it should return ERR_PTR(error).
170 be attached; creation of new superblock is a common side effect.
172 The most interesting member of the superblock structure that the
189 struct super_block *sb: the superblock structure. The callback
201 A superblock object represents a mounted filesystem.
207 This describes how the VFS can manipulate the superblock of your
273 put_super: called when the VFS wishes to free the superblock
274 (i.e. unmount). This is called with the superblock lock held
276 write_super: called when the VFS superblock needs to be written to
[all …]
|
| D | ext3.txt | 109 specified in the superblock, which can be
127 sb=n Use alternate superblock at this location.
|
| D | gfs2-uevents.txt | 96 into the filesystem superblock. If it exists, this will
|
| D | automount-support.txt | 23 superblock and gain a vfsmount structure representing it.
|
| D | sysv-fs.txt | 23 The superblock is only searched in the blocks 9, 15, 18, which
|
| /linux-3.4.99/drivers/md/persistent-data/ |
| D | dm-space-map-metadata.h | 24 dm_block_t superblock);
|
| D | dm-block-manager.h | 117 struct dm_block *superblock);
|
| D | dm-space-map-metadata.c | 541 dm_block_t superblock) in dm_sm_metadata_create() argument
548 smm->begin = superblock + 1; in dm_sm_metadata_create()
569 for (i = superblock; !r && i < smm->begin; i++) in dm_sm_metadata_create()
|
| D | dm-block-manager.c | 585 struct dm_block *superblock) in dm_bm_flush_and_unlock() argument
596 dm_bm_unlock(superblock); in dm_bm_flush_and_unlock()
|
| /linux-3.4.99/fs/befs/ |
| D | TODO | 13 representations of the superblock and inode.
|
| 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-3.4.99/fs/cramfs/ |
| D | README | 13 <superblock>
17 <superblock>: struct cramfs_super (see cramfs_fs.h).
91 The superblock ought to indicate the block size that the fs was
120 data, only the superblock, inodes and block pointers.
|
| /linux-3.4.99/fs/btrfs/ |
| D | check-integrity.c | 2126 struct btrfsic_block *const superblock, in btrfsic_process_written_superblock() argument
2131 superblock->generation = btrfs_super_generation(super_hdr); in btrfsic_process_written_superblock()
2132 if (!(superblock->generation > state->max_superblock_generation || in btrfsic_process_written_superblock()
2138 (unsigned long long)superblock->logical_bytenr, in btrfsic_process_written_superblock()
2139 superblock->dev_state->name, in btrfsic_process_written_superblock()
2140 (unsigned long long)superblock->dev_bytenr, in btrfsic_process_written_superblock()
2141 superblock->mirror_num, in btrfsic_process_written_superblock()
2151 (unsigned long long)superblock->logical_bytenr, in btrfsic_process_written_superblock()
2152 superblock->dev_state->name, in btrfsic_process_written_superblock()
2153 (unsigned long long)superblock->dev_bytenr, in btrfsic_process_written_superblock()
[all …]
|
| /linux-3.4.99/Documentation/ |
| D | md.txt | 49 superblock can be autodetected and run at boot time.
82 The md driver can support a variety of different superblock formats.
83 Currently, it supports superblock formats "0.90.0" and the "md-1" format
86 The kernel will autodetect which format superblock is being used.
89 reasons - it is the original superblock format.
92 General Rules - apply for all superblock formats
110 version number. The major version number selects which superblock
113 superblock.
122 appropriate superblock written to them, and then passed be in with
130 arrays with no superblock (non-persistent).
[all …]
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-fs-ext4 | 16 stripe size is not set in the ext4 superblock
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | persistent-data.txt | 48 ensures that all data is flushed before it writes the superblock.
|
| D | dm-raid.txt | 74 # No metadata devices specified to hold superblock/bitmap info
|