Lines Matching +full:block +full:- +full:number

2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
6 block devices using a cryptographic digest provided by the kernel crypto API.
7 This target is read-only.
21     This is the type of the on-disk hash format.
25       the rest of the block is padded with zeroes.
33     checked.  It may be specified as a path, like /dev/sdaX, or a device number,
40     dm-verity device.
43     The block size on a data device in bytes.
44     Each block corresponds to one digest on the hash device.
47     The size of a hash block in bytes.
50     The number of data blocks on the data device.  Additional blocks are
55     This is the offset, in <hash_block_size>-blocks, from the start of hash_dev
56     to the root block of the hash tree.
63     The hexadecimal encoding of the cryptographic hash of the root hash block
71     Number of optional parameters. If there are no optional parameters,
73     Otherwise #opt_params is the number of following arguments.
82     Restart the system when a corrupted block is discovered. This option is
87     Panic the device when a corrupted block is discovered. This option is
113     Note: block sizes for data and hash devices must match. Also, if the
117     Number of generator roots. This equals to the number of parity bytes in
118     the encoding data. For example, in RS(M, N) encoding, the number of roots
119     is M-N.
122     The number of encoding data blocks on the FEC device. The block size for
131     rather than every time.  This reduces the overhead of dm-verity so that it
138     blocks, and a hash block will not be verified any more after all the data
144     the root hash during the creation of the device mapper block device.
167 dm-verity is meant to be set up as part of a verified boot path.  This
169 booting from a known-good device (like a USB drive or CD).
171 When a dm-verity device is configured, it is expected that the caller
173 After instantiation, all hashes will be verified on-demand during
179 per-block basis. This allows for a lightweight hash computation on first read
180 into the page cache. Block hashes are stored linearly, aligned to the nearest
181 block size.
189 ---------
192 of some data block on disk is calculated. If it is an intermediary node,
193 the hash of a number of child nodes is calculated.
196 block.  The number is determined based on block_size and the size of the
197 selected cryptographic digest algorithm.  The hashes are linearly-ordered in
216 On-disk format
219 The verity kernel code does not read the verity metadata on-disk header.
221 It is expected that a user-space tool will verify the integrity of the
225 be passed via the kernel command-line in a rooted chain of trust where
226 the command-line is verified.
228 Directly following the header (and with sector number padded to the next hash
229 block boundary) are the hash blocks which are stored a depth at a time
232 The full specification of kernel parameters and on-disk metadata format
246   # dmsetup create vroot --readonly --table \