Lines Matching +full:i +full:- +full:cache +full:- +full:block +full:- +full:size

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.
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.
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
82     Restart the system when a corrupted block is discovered. This option is
100     Note: block sizes for data and hash devices must match. Also, if the
106     is M-N.
109     The number of encoding data blocks on the FEC device. The block size for
118     rather than every time.  This reduces the overhead of dm-verity so that it
125     blocks, and a hash block will not be verified any more after all the data
131     the root hash during the creation of the device mapper block device.
138 dm-verity is meant to be set up as part of a verified boot path.  This
140 booting from a known-good device (like a USB drive or CD).
142 When a dm-verity device is configured, it is expected that the caller
144 After instantiation, all hashes will be verified on-demand during
146 tree, the root hash, then the I/O will fail.  This should detect
150 per-block basis. This allows for a lightweight hash computation on first read
151 into the page cache. Block hashes are stored linearly, aligned to the nearest
152 block size.
160 ---------
163 of some data block on disk is calculated. If it is an intermediary node,
167 block.  The number is determined based on block_size and the size of the
168 selected cryptographic digest algorithm.  The hashes are linearly-ordered in
187 On-disk format
190 The verity kernel code does not read the verity metadata on-disk header.
192 It is expected that a user-space tool will verify the integrity of the
196 be passed via the kernel command-line in a rooted chain of trust where
197 the command-line is verified.
200 block boundary) are the hash blocks which are stored a depth at a time
203 The full specification of kernel parameters and on-disk metadata format
217   # dmsetup create vroot --readonly --table \