-
Notifications
You must be signed in to change notification settings - Fork 19
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
Remove kernel bug workaround for fwErr outside EIO #5
Comments
deeglaze
added a commit
to deeglaze/go-sev-guest
that referenced
this issue
Mar 19, 2023
The IV reuse fix 47894e0fa6a5 works against the host's throttling by making the sev-guest device useless when throttled. The x86/urgent fix 72f7754dcf31 that merged to tip on March 16 still hasn't made it to some distros, so this workaround is still needed temporarily. Issue google#40 is to revert this change at the appropriate time. The same fix for google#40 includes the fix for google#5. Signed-off-by: Dionna Glaze <[email protected]>
deeglaze
added a commit
to deeglaze/go-sev-guest
that referenced
this issue
Mar 19, 2023
The IV reuse fix 47894e0fa6a5 works against the host's throttling by making the sev-guest device useless when throttled. The x86/urgent fix 72f7754dcf31 that merged to tip on March 16 still hasn't made it to some distros, so this workaround is still needed temporarily. Issue google#40 is to revert this change at the appropriate time. The same fix for google#40 includes the fix for google#5. Signed-off-by: Dionna Glaze <[email protected]>
deeglaze
added a commit
to deeglaze/go-sev-guest
that referenced
this issue
May 2, 2023
The IV reuse fix 47894e0fa6a5 works against the host's throttling by making the sev-guest device useless when throttled. The x86/urgent fix 72f7754dcf31 that merged to tip on March 16 still hasn't made it to some distros, so this workaround is still needed temporarily. Issue google#40 is to revert this change at the appropriate time. The same fix for google#40 includes the fix for google#5. Signed-off-by: Dionna Glaze <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the guest kernel patches are fixed to remove the uninitialized memory from the response, we can remove our check for EIO to avoid doing anything to the firmware error value. Added in PR#3
The text was updated successfully, but these errors were encountered: