init: always run cryptsetup hook with secure boot #3485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Init hooks specify an *_enabled function that determines whether or not the hook is skipped during boot. Hooks are run by the "init" script, shipped as part of the initramfs-framework poky recipe.
Several conditions were checked in the cryptsetup-efi-tpm enablement function, some of which could cause the hook to be improperly skipped.
Force the hook to run when in secure boot user mode, as we want any failure in the hook's run function to be detected and abort the boot.
Change-type: patch
Contributor checklist
Change-type
present on at least one commitSigned-off-by
is presentReviewer Guidelines