-
Notifications
You must be signed in to change notification settings - Fork 9
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
kata: use restrictive default policy #759
Conversation
iirc the 0003 patch is already a modified version of the upstream PR, isn't it? |
It sure looks different :) Should I then just merge the two? |
idk, both fine for me. Costs nothing to add a patch and provide some history, might also be easier to roll-back if needed. Whatever you do, please document it properly (would also be nice if you could try to improve the comment of the existing patch), as it is obviously not covering all relevant points. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having the new patch seems reasonable to me. Didn't test this yet on m50-ganondorf.
packages/by-name/kata/kata-runtime/0004-runtime-set-mrconfigid-if-running-in-TDX.patch
Outdated
Show resolved
Hide resolved
Yes, I had to resolve some merge conflicts, so the bug was introduced by me. |
Co-authored-by: Moritz Sanft <[email protected]>
Everything addressed. @katexochen please check the patch docstring. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doc comment looks good, thanks! (didn't test the change)
There's a bug in patch 0003 which causes wrong arguments for QEMU and thus prevents starting VMs
- patch 0004 in this PR fixes that bug. Since 0003 corresponds to an open upstream PR, I'd rather not integrate the patch here into 0003, so that we have a clear history of the modifications.There was another bug in the upstream PR, which assumed hex encoding for MRCONFIGID where it should have been base64.
I amended 0003 to fix these, and subsequently changed to a restrictive default policy.