[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <85baa45b-0fb9-43fb-9f87-9b0036e08f56@vates.tech>
Date: Thu, 04 Dec 2025 13:21:49 +0000
From: "Thomas Courrege" <thomas.courrege@...es.tech>
To: "Tom Lendacky" <thomas.lendacky@....com>, pbonzini@...hat.com, seanjc@...gle.com, corbet@....net, ashish.kalra@....com, john.allen@....com, herbert@...dor.apana.org.au, nikunj@....com
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org
Subject: Re: [PATCH v2] KVM: SEV: Add KVM_SEV_SNP_HV_REPORT_REQ command
On 12/2/25 8:29 PM, Tom Lendacky wrote:
>> +
>> +e_free_rsp:
>> + /* contains sensitive data */
>> + memzero_explicit(report_rsp, PAGE_SIZE);
> Does it? What is sensitive that needs to be cleared?
Combine with others reports, it could allow to do an inventory of the guests,
which ones share the same author, measurement, policy...
It is not needed, but generating a report is not a common operation so
performance is not an issue here. What do you think is the best to do ?
Regards,
Thomas
Powered by blists - more mailing lists