diff options
| author | Alper Gun <[email protected]> | 2021-06-10 17:46:04 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-06-11 11:52:48 -0400 |
| commit | 934002cd660b035b926438244b4294e647507e13 (patch) | |
| tree | c778e64331b20b6fc52053468c584c51a0a3378a /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 (diff) | |
KVM: SVM: Call SEV Guest Decommission if ASID binding fails
Send SEV_CMD_DECOMMISSION command to PSP firmware if ASID binding
fails. If a failure happens after a successful LAUNCH_START command,
a decommission command should be executed. Otherwise, guest context
will be unfreed inside the AMD SP. After the firmware will not have
memory to allocate more SEV guest context, LAUNCH_START command will
begin to fail with SEV_RET_RESOURCE_LIMIT error.
The existing code calls decommission inside sev_unbind_asid, but it is
not called if a failure happens before guest activation succeeds. If
sev_bind_asid fails, decommission is never called. PSP firmware has a
limit for the number of guests. If sev_asid_binding fails many times,
PSP firmware will not have resources to create another guest context.
Cc: [email protected]
Fixes: 59414c989220 ("KVM: SVM: Add support for KVM_SEV_LAUNCH_START command")
Reported-by: Peter Gonda <[email protected]>
Signed-off-by: Alper Gun <[email protected]>
Reviewed-by: Marc Orr <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Message-Id: <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions