Lines Matching full:sector
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.
13 writes sector data and integrity tags into a journal, commits the journal
53 2. load the dm-integrity target with one-sector size, the kernel driver
67 2. the number of reserved sector at the beginning of the device - the
155 an attacker reading the journal could see the last sector numbers
156 that were written. From the sector numbers, the attacker can infer
161 Protect sector numbers in the journal from accidental or malicious
168 the journal. Thus, modified sector number would be detected at
265 * logical sector (specifies where the data and tag should
270 - every metadata sector ends with
273 64-byte value. It is used to store hmac of sector
275 possibility that the attacker tampers with sector
282 - every sector in the data area contains:
289 512-byte sector of the journal ends with 8-byte commit id. If the
299 sector in the data area. The size of this area is always 4KiB or