Searched refs:hash_dev (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/drivers/md/ |
| H A D | dm-verity-target.c | 858 v->hash_dev->name, in verity_status()
921 DMEMIT(",hash_device_name=%s", v->hash_dev->name); in verity_status()
1017 if (v->hash_dev) in verity_dtr()
1018 dm_put_device(ti, v->hash_dev); in verity_dtr()
1276 r = dm_get_device(ti, argv[2], BLK_OPEN_READ, &v->hash_dev); in verity_ctr()
1294 num < bdev_logical_block_size(v->hash_dev->bdev) || in verity_ctr()
1456 v->bufio = dm_bufio_client_create(v->hash_dev->bdev, in verity_ctr()
|
| H A D | dm-verity.h | 38 struct dm_dev *hash_dev; member
|
| /openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
| H A D | image_types_verity.bbclass | 19 # verity 1 <dev> <hash_dev> \
25 # As the hash tree data is found at the end of the image, <dev> and <hash_dev>
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 14 <version> <dev> <hash_dev>
36 <hash_dev>
55 This is the offset, in <hash_block_size>-blocks, from the start of hash_dev
|