Home
last modified time | relevance | path

Searched refs:hash_start (Results 1 – 6 of 6) sorted by relevance

/linux/security/integrity/ima/ !
H A Dima_appraise.c284 int rc = -EINVAL, hash_start = 0; in xattr_verify() local
290 hash_start = 1; in xattr_verify()
306 if (xattr_len - sizeof(xattr_value->type) - hash_start >= in xattr_verify()
312 rc = memcmp(&xattr_value->data[hash_start], in xattr_verify()
/linux/drivers/md/ !
H A Ddm-verity.h52 sector_t hash_start; /* hash start in blocks */ member
H A Ddm-verity-fec.c253 block += v->hash_start; in fec_read_bufs()
428 block = block - v->hash_start + v->data_blocks; in verity_fec_decode()
689 hash_blocks = v->hash_blocks - v->hash_start; in verity_fec_ctr()
/linux/drivers/crypto/amcc/ !
H A Dcrypto4xx_alg.c491 static int crypto4xx_compute_gcm_hash_key_sw(__le32 *hash_start, const u8 *key, in crypto4xx_compute_gcm_hash_key_sw() argument
505 crypto4xx_memcpy_to_le32(hash_start, src, 16); in crypto4xx_compute_gcm_hash_key_sw()
/linux/drivers/crypto/starfive/ !
H A Djh7110-hash.c225 goto hash_start; in starfive_hash_one_request()
241 hash_start: in starfive_hash_one_request()
/linux/Documentation/admin-guide/device-mapper/ !
H A Dverity.rst39 same device is used, the hash_start should be outside the configured