Lines Matching refs:integrity

2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
8 A general problem with storing integrity tags with every sector is that
9 writing the sector and the integrity tag must be atomic - i.e. in case of
10 crash, either both sector and integrity tag or none of them is written.
12 To guarantee write atomicity, the dm-integrity target uses journal, it
13 writes sector data and integrity tags into a journal, commits the journal
14 and then copies the data and integrity tags to their respective location.
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
23 The dm-integrity target can also be used as a standalone target, in this
24 mode it calculates and verifies the integrity tag internally. In this
25 mode, the dm-integrity target can be used to detect silent data
28 There's an alternate mode of operation where dm-integrity uses bitmap
30 region's data and integrity tags are not synchronized - if the machine
38 zeroes. If the superblock is neither valid nor zeroed, the dm-integrity
44 2. load the dm-integrity target with one-sector size, the kernel driver
46 3. unload the dm-integrity target
48 5. load the dm-integrity target with the target size
50 6. if you want to use dm-integrity with dm-crypt, load the dm-crypt target
59    dm-integrity won't read of write these sectors
61 3. the size of the integrity tag (if "-" is used, the size is taken from
68 		not used and data sectors and integrity tags are written
70 		and integrity tag doesn't match.
72 		data and integrity tags are written to the
125 	When this argument is used, the dm-integrity target won't accept
126 	integrity tags from the upper target, but it will automatically
127 	generate and verify the integrity tags.
129 	You can use a crc algorithm (such as crc32), then integrity target
135 	When this argument is not used, the integrity tags are accepted
137 	target should check the validity of the integrity tags.
140 	Recalculate the integrity tags automatically. It is only valid
162 	mode, the integrity of journal entries is checked when replaying
168 	less overhead there is for per-block integrity metadata.
186 	Allow block discard requests (a.k.a. TRIM) for the integrity device.
198 1. the number of integrity mismatches
215 	* integrity tag size
241 		* integrity tag (the size is specified in the superblock)
271 	* tag area - it contains integrity tags. There is one tag for each