Lines Matching refs:sector
2 per-sector tags that can be used for storing integrity information.
4 A general problem with storing integrity tags with every sector is that
5 writing the sector and the integrity tag must be atomic - i.e. in case of
6 crash, either both sector and integrity tag or none of them is written.
9 writes sector data and integrity tags into a journal, commits the journal
32 2. load the dm-integrity target with one-sector size, the kernel driver
46 2. the number of reserved sector at the beginning of the device - the
127 an attacker reading the journal could see the last sector nubmers
128 that were written. From the sector numbers, the attacker can infer
133 Protect sector numbers in the journal from accidental or malicious
140 the journal. Thus, modified sector number would be detected at
175 * logical sector (specifies where the data and tag should
179 every metadata sector ends with
181 64-byte value. It is used to store hmac of sector
183 possibility that the attacker tampers with sector
188 every sector in the data area contains:
193 512-byte sector of the journal ends with 8-byte commit id. If the
200 sector in the data area