Introduce ".loader" section manifesting the default next boot target - #826
Open
vittyvk wants to merge 1 commit into
Open
Introduce ".loader" section manifesting the default next boot target#826vittyvk wants to merge 1 commit into
vittyvk wants to merge 1 commit into
Conversation
Offline PCR prediction without fallback CSV file requires the knowledge of
the next boot target after shim. While this is normally "grub{arch}.efi" in
the vendor directory where shim binary is (or just in 'BOOT'), it is also
customizable via DEFAULT_LOADER. Introduce a new section in shim binary and
export the information explicitly.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #826 +/- ##
==========================================
- Coverage 59.48% 58.77% -0.71%
==========================================
Files 24 24
Lines 4226 4226
Branches 655 654 -1
==========================================
- Hits 2514 2484 -30
Misses 1471 1471
- Partials 241 271 +30 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Offline PCR prediction without fallback CSV file (or with CSV file specifying just shim itself) requires the knowledge of the next boot target after shim. While this is normally "grub{arch}.efi" in the vendor directory where shim binary is (or just in 'BOOT'), it is also customizable via DEFAULT_LOADER. Introduce a new section in shim binary and export the information explicitly.