mok: Add a building option to avoid the vendor_dbx being appended to … #779
Conversation
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
…MokListRT The new building option DISABLE_APPEND_V_DBX_TO_MOKX avoids appending the vendor_dbx to MokListRT. Instead, the vendor_dbx will be exposed through the mok config table space. As the vendor-dbx grows, it caused some problems when writing such a large variable. Some firmwares lie the avaiable space [1], and some even crash [2] for no good reason after the writing of MokListXRT. If your shim and kernel don't rely on MokListXRT to block anything, you can use this building option to expose vendor_dbx through the mok config table instead of appending it to MokListRT. Link: https://bugzilla.suse.com/show_bug.cgi?id=1185261 [1] Link: rhboot#369 (comment) [2] Signed-off-by: Chun-Yi Lee <jlee@suse.com>
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.
…MokListRT
The new building option DISABLE_APPEND_V_DBX_TO_MOKX avoids appending the vendor_dbx to MokListRT. Instead, the vendor_dbx will be exposed through the mok config table space.
As the vendor-dbx grows, it caused some problems when writing such a large variable. Some firmwares lie the avaiable space [1], and some even crash [2] for no good reason after the writing of MokListXRT. If your shim and kernel don't rely on MokListXRT to block anything, you can use this building option to expose vendor_dbx through the mok config table instead of appending it to MokListRT.
Link: https://bugzilla.suse.com/show_bug.cgi?id=1185261 [1]
Link: #369 (comment) [2]