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
44 2. load the dm-integrity target with one-sector size, the kernel driver
58 2. the number of reserved sector at the beginning of the device - the
150 an attacker reading the journal could see the last sector numbers
151 that were written. From the sector numbers, the attacker can infer
156 Protect sector numbers in the journal from accidental or malicious
163 the journal. Thus, modified sector number would be detected at
255 * logical sector (specifies where the data and tag should
260 - every metadata sector ends with
263 64-byte value. It is used to store hmac of sector
265 possibility that the attacker tampers with sector
272 - every sector in the data area contains:
279 512-byte sector of the journal ends with 8-byte commit id. If the
289 sector in the data area