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

mok: relax the maximum variable size check #369

Merged
merged 1 commit into from
Jul 20, 2021

Conversation

lcp
Copy link
Collaborator

@lcp lcp commented May 6, 2021

Some UEFI environment such as u-boot doesn't implement
QueryVariableInfo(), so we couldn't rely on the function to estimate the
available space for RT variables. All we can do is to call SetVariable()
directly and check the return value of SetVariable().

Signed-off-by: Gary Lin [email protected]

Some UEFI environment such as u-boot doesn't implement
QueryVariableInfo(), so we couldn't rely on the function to estimate the
available space for RT variables. All we can do is to call SetVariable()
directly and check the return value of SetVariable().

Signed-off-by: Gary Lin <[email protected]>
@julian-klode
Copy link
Collaborator

It's worth pointing out that some firmware implementations (Apple 2.40) even lie and tell you they have space but then die/hang when you try to write :D

@lcp
Copy link
Collaborator Author

lcp commented Jun 7, 2021

We had a similar case that the firmware lied about the space, but the firmware kindly returned EFI_OUT_OF_RESOURCES :-p

#372

@julian-klode
Copy link
Collaborator

+1 on merging

We got hit by this too https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780 and verified this fixes it. Thanks!

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.

3 participants