mirror of
https://git.yoctoproject.org/meta-security
synced 2026-05-07 04:58:47 +00:00
Since dm-verity-image.bbclass effectively injects <DM_VERITY_IMAGE>:do_image_<DM_VERITY_IMAGE_TYPE> dependency for do_image_wic task, we can change verity rootfs artifact reference here from DEPLOY_DIR_IMAGE to IMGDEPLOYDIR in order to mitigate following breakage which was observed when bitbaking <DM_VERITY_IMAGE> target from scratch (using sstate-cache provided artifacts): | wic.filemap.Error: cannot open image file '.../build/tmp/deploy/images/beaglebone-yocto/core-image-minimal-beaglebone-yocto.ext4.verity': [Errno 2] No such file or directory: '.../build/tmp/deploy/images/beaglebone-yocto/core-image-minimal-beaglebone-yocto.ext4.verity' | WARNING: exit code 1 from a shell command. | ERROR: Task (.../meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1' Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
16 lines
818 B
Plaintext
16 lines
818 B
Plaintext
# SPDX-License-Identifier: MIT
|
|
#
|
|
# Copyright (C) 2020 BayLibre SAS
|
|
# Author: Bartosz Golaszewski <bgolaszewski@baylibre.com>
|
|
#
|
|
# A dm-verity variant of the regular wks for beaglebone black. We need to fetch
|
|
# the partition images from the DEPLOY_DIR_IMAGE as the rootfs source plugin will
|
|
# not recreate the exact block device corresponding with the hash tree. We must
|
|
# not alter the label or any other setting on the image.
|
|
#
|
|
# This .wks only works with the dm-verity-img class.
|
|
|
|
part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4 --size 16 --sourceparams="loader=u-boot" --use-uuid
|
|
part / --source rawcopy --ondisk mmcblk0 --sourceparams="file=${IMGDEPLOYDIR}/${DM_VERITY_IMAGE}-${MACHINE}.${DM_VERITY_IMAGE_TYPE}.verity"
|
|
bootloader --append="console=ttyS0,115200"
|