diff options
| author | Kevin Hao <kexin.hao@windriver.com> | 2023-03-15 10:12:24 +0800 |
|---|---|---|
| committer | Armin Kuster <akuster808@gmail.com> | 2023-03-20 16:27:24 -0400 |
| commit | a7f73ab5918c79fcaec7d6638a2f801c8dc2aeb9 (patch) | |
| tree | 98ea713718518e416c9cdb425d374839f1df90f7 /dynamic-layers | |
| parent | 2b2b112b056e2e01d00e6905b8908bbde0e3a8de (diff) | |
| download | meta-security-a7f73ab5918c79fcaec7d6638a2f801c8dc2aeb9.tar.gz | |
dm-verity-img.bbclass: Fix the hash offset alignment issue
When using the kernel module parameter "dm-mod.create=" [1] to create
the device-mapper device, the hash offset address we passed to kernel
module is the hash block number. That means the hash offset address
would have to be aligned to the max(data_block_size, hash_block_size),
otherwise there would be no way to set the correct hash offset address
via "dm-mo.create=".
[1] https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/dm-init.rst
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'dynamic-layers')
0 files changed, 0 insertions, 0 deletions