Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tpm: Boot with a warning if the event log is full #657

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kukrimate
Copy link

@kukrimate kukrimate commented Apr 18, 2024

The extend operation still occurs even if *_log_extend_event
returns EFI_VOLUME_FULL.

Let's print a warning when we first see this error code, but otherwise
continue booting.

Bailing on this condition has caused machines with limited event log
space to become unbootable with TPM 2.0 enabled. (fixes #654)

@vathpela
Copy link
Contributor

vathpela commented May 8, 2024

Yeah, I'd like to see it logged once. Otherwise this looks reasonable.

@kukrimate kukrimate force-pushed the main branch 2 times, most recently from b48ac61 to b6a284a Compare October 22, 2024 07:33
The extend operation still occurs even if `*_log_extend_event`
returns EFI_VOLUME_FULL.

Let's print a warning when we first see this error code, but otherwise
continue booting.

Bailing on this condition has caused machines with limited event log
space to become unbootable with TPM 2.0 enabled. (fixes rhboot#654)

Signed-off-by: Mate Kukri <[email protected]>
@kukrimate
Copy link
Author

@vathpela Added the warning, and it should cover all places the EFI_VOLUME_FULL thing can be returned to represent this condition.

@kukrimate kukrimate changed the title tpm: Don't return an error if event log is full tpm: Boot with a warning if the event log is full Oct 22, 2024
@marosg42
Copy link

@kukrimate in https://bugs.launchpad.net/ubuntu/+source/shim/+bug/2089320 you mentioned this should solve it. Any chance this can get merged?

Copy link

@sgtsnookums sgtsnookums left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ran into this exact underlying issue this week, found the issue and this PR in github, and tried applying this patch, which solved my issue booting with the latest upstream UEFI dbx entries. Take my thumbs up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Too big dbx causes Shim to refuse to boot, presumably due to "failure" from tpm2->hash_log_extend_event()
4 participants