Lines Matching +full:os +full:- +full:code +full:- +full:offset

2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
7 This target is read-only.
21     This is the type of the on-disk hash format.
23     0 is the original format used in the Chromium OS.
40     dm-verity device.
55     This is the offset, in <hash_block_size>-blocks, from the start of hash_dev
110     is M-N.
116 fec_start <offset>
117     This is the offset, in <data_block_size> blocks, from the start of the
122     rather than every time.  This reduces the overhead of dm-verity so that it
158 dm-verity is meant to be set up as part of a verified boot path.  This
160 booting from a known-good device (like a USB drive or CD).
162 When a dm-verity device is configured, it is expected that the caller
164 After instantiation, all hashes will be verified on-demand during
170 per-block basis. This allows for a lightweight hash computation on first read
180 ---------
188 selected cryptographic digest algorithm.  The hashes are linearly-ordered in
207 On-disk format
210 The verity kernel code does not read the verity metadata on-disk header.
212 It is expected that a user-space tool will verify the integrity of the
216 be passed via the kernel command-line in a rooted chain of trust where
217 the command-line is verified.
223 The full specification of kernel parameters and on-disk metadata format
237   # dmsetup create vroot --readonly --table \