From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
Dov Murik <dovmurik@linux.ibm.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Tobin Feldman-Fitzthum <tobin@ibm.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
James Bottomley <jejb@linux.ibm.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Michael Roth <michael.roth@amd.com>,
"Xu, Min M" <min.m.xu@intel.com>,
Tobin Feldman-Fitzthum <tobin@linux.ibm.com>
Subject: Re: [PATCH v2 1/1] OvmfPkg/AmdSev/SecretDxe: Allocate CC secret location as EfiACPIReclaimMemory
Date: Thu, 15 Dec 2022 02:42:12 +0000 [thread overview]
Message-ID: <MW4PR11MB5872B7D19CBF6BDC7DA6C0138CE19@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6e26dd9a-b3f1-5815-a743-0b8889ab6fe6@amd.com>
Hey
CI failed - https://github.com/tianocore/edk2/pull/3772
Have you run CI before submit patch? Please take a look.
Thank you
Yao, Jiewen
> -----Original Message-----
> From: Tom Lendacky <thomas.lendacky@amd.com>
> Sent: Monday, December 12, 2022 11:01 PM
> To: Dov Murik <dovmurik@linux.ibm.com>; devel@edk2.groups.io
> Cc: Tobin Feldman-Fitzthum <tobin@ibm.com>; Ard Biesheuvel
> <ardb+tianocore@kernel.org>; Aktas, Erdem <erdemaktas@google.com>;
> Gerd Hoffmann <kraxel@redhat.com>; James Bottomley
> <jejb@linux.ibm.com>; Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan
> L <jordan.l.justen@intel.com>; Michael Roth <michael.roth@amd.com>; Xu,
> Min M <min.m.xu@intel.com>; Tobin Feldman-Fitzthum
> <tobin@linux.ibm.com>
> Subject: Re: [PATCH v2 1/1] OvmfPkg/AmdSev/SecretDxe: Allocate CC secret
> location as EfiACPIReclaimMemory
>
> On 12/12/22 02:08, Dov Murik wrote:
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4186
> >
> > Commit 079a58276b98 ("OvmfPkg/AmdSev/SecretPei: Mark SEV launch
> secret
> > area as reserved") marked the launch secret area itself (1 page) as
> > reserved so the guest OS can use it during the lifetime of the OS.
> > However, the address and size of the secret area held in the
> > CONFIDENTIAL_COMPUTING_SECRET_LOCATION struct are declared as
> STATIC in
> > OVMF (in AmdSev/SecretDxe); therefore there's no guarantee that it will
> > not be written over by OS data.
> >
> > Fix this by allocating the memory for the
> > CONFIDENTIAL_COMPUTING_SECRET_LOCATION struct with the
> > EfiACPIReclaimMemory memory type to ensure the guest OS will not reuse
> > this memory.
> >
> > Fixes: 079a58276b98 ("OvmfPkg/AmdSev/SecretPei: Mark SEV launch
> secret area as reserved")
> > Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> > Cc: Erdem Aktas <erdemaktas@google.com>
> > Cc: Gerd Hoffmann <kraxel@redhat.com>
> > Cc: James Bottomley <jejb@linux.ibm.com>
> > Cc: Jiewen Yao <Jiewen.Yao@intel.com>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Cc: Michael Roth <michael.roth@amd.com>
> > Cc: Min Xu <min.m.xu@intel.com>
> > Cc: Tobin Feldman-Fitzthum <tobin@linux.ibm.com>
> > Cc: Tom Lendacky <thomas.lendacky@amd.com>
> > Signed-off-by: Dov Murik <dovmurik@linux.ibm.com>
>
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
>
> >
> > ---
> >
> > v2 changes:
> > * Allocate with EfiACPIReclaimMemory memory type (thanks Ard)
> > ---
> > OvmfPkg/AmdSev/SecretDxe/SecretDxe.c | 22 ++++++++++++++------
> > 1 file changed, 16 insertions(+), 6 deletions(-)
> >
> > diff --git a/OvmfPkg/AmdSev/SecretDxe/SecretDxe.c
> b/OvmfPkg/AmdSev/SecretDxe/SecretDxe.c
> > index 3d84b2545052..4f65b1ce5ba5 100644
> > --- a/OvmfPkg/AmdSev/SecretDxe/SecretDxe.c
> > +++ b/OvmfPkg/AmdSev/SecretDxe/SecretDxe.c
> > @@ -8,11 +8,6 @@
> > #include <Library/UefiBootServicesTableLib.h>
> > #include <Guid/ConfidentialComputingSecret.h>
> >
> > -STATIC CONFIDENTIAL_COMPUTING_SECRET_LOCATION
> mSecretDxeTable = {
> > - FixedPcdGet32 (PcdSevLaunchSecretBase),
> > - FixedPcdGet32 (PcdSevLaunchSecretSize),
> > -};
> > -
> > EFI_STATUS
> > EFIAPI
> > InitializeSecretDxe (
> > @@ -20,8 +15,23 @@ InitializeSecretDxe (
> > IN EFI_SYSTEM_TABLE *SystemTable
> > )
> > {
> > + EFI_STATUS Status;
> > + CONFIDENTIAL_COMPUTING_SECRET_LOCATION *SecretDxeTable;
> > +
> > + Status = gBS->AllocatePool (
> > + EfiACPIReclaimMemory,
> > + sizeof (CONFIDENTIAL_COMPUTING_SECRET_LOCATION),
> > + (VOID **)&SecretDxeTable
> > + );
> > + if (EFI_ERROR (Status)) {
> > + return Status;
> > + }
> > +
> > + SecretDxeTable->Base = FixedPcdGet32 (PcdSevLaunchSecretBase);
> > + SecretDxeTable->Size = FixedPcdGet32 (PcdSevLaunchSecretSize);
> > +
> > return gBS->InstallConfigurationTable (
> > &gConfidentialComputingSecretGuid,
> > - &mSecretDxeTable
> > + SecretDxeTable
> > );
> > }
next prev parent reply other threads:[~2022-12-15 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 8:08 [PATCH v2 1/1] OvmfPkg/AmdSev/SecretDxe: Allocate CC secret location as EfiACPIReclaimMemory Dov Murik
2022-12-12 15:00 ` Lendacky, Thomas
2022-12-15 2:42 ` Yao, Jiewen [this message]
2022-12-15 6:33 ` Dov Murik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MW4PR11MB5872B7D19CBF6BDC7DA6C0138CE19@MW4PR11MB5872.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox