From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, guomin.jiang@intel.com
Cc: Jian J Wang <jian.j.wang@intel.com>,
Hao A Wu <hao.a.wu@intel.com>, Dandan Bi <dandan.bi@intel.com>,
Liming Gao <liming.gao@intel.com>,
Debkumar De <debkumar.de@intel.com>,
Harry Han <harry.han@intel.com>,
Catharine West <catharine.west@intel.com>
Subject: Re: [edk2-devel] [PATCH v7 10/10] MdeModulePkg/Core: Avoid redundant shadow when enable the Migrated PCD (CVE-2019-11098)
Date: Thu, 23 Jul 2020 00:53:06 +0200 [thread overview]
Message-ID: <bfbffc42-da7c-e57f-745f-4ffea80530ed@redhat.com> (raw)
In-Reply-To: <20200722083657.739-11-guomin.jiang@intel.com>
On 07/22/20 10:36, Guomin Jiang wrote:
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1614
>
> When PcdMigrateTemporaryRamFirmwareVolumes is TRUE, it will shadow the
> PEIMs, when it is disabled, PEIMs marked REGISTER_FOR_SHADOW will be
> shadowed as well and it is controled by PcdShadowPeimOnBoot and
> PcdShadowPeimOnS3Boot.
>
> To cover the shadow behavior, the change will always shadow PEIMs when
> enable PcdMigrateTemporaryRamFirmwareVolumes.
>
> When PcdMigrateTemporaryRamFirmwareVolumes is true, if enable
> PcdShadowPeimOnBoot or PcdShadowPeimOnS3Boot, it will shadow some PEIMs
> twice and occupy more memory and waste more boot time, it is unnecessary,
> so the only valid choice is to enable PcdMigrateTemporaryRamFirmwareVolumes
> and disable PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot.
>
> Signed-off-by: Guomin Jiang <guomin.jiang@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Dandan Bi <dandan.bi@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Debkumar De <debkumar.de@intel.com>
> Cc: Harry Han <harry.han@intel.com>
> Cc: Catharine West <catharine.west@intel.com>
> ---
> MdeModulePkg/MdeModulePkg.dec | 11 +++++---
> MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c | 14 +++++++---
> MdeModulePkg/Core/Pei/Image/Image.c | 6 ++---
> MdeModulePkg/Core/Pei/PeiMain/PeiMain.c | 26 +++++++++++++++----
> 4 files changed, 42 insertions(+), 15 deletions(-)
(1) This patch should be split, and the parts coming out of it should be
squashed into:
- patch#1 ("MdeModulePkg: Add new PCD to control the evacuate temporary
memory feature"),
- and patch#2 ("MdeModulePkg/PeiCore: Enable T-RAM evacuation in
PeiCore").
It's wrong to introduce a feature with a known bug in one patch of a
series, and then fix it separately in a later patch in the same series.
If the bug is known in the earlier patch, at the time of posting the
series, then the earlier patch should be updated to *not* introduce the
bug in the first place.
Note: when you do the above squashing, you're going to modify both
patches #1 and #2 significantly, so you'll have to drop all feedback
tags from them (received thus far), and reviewers will have to re-check
both of those patches.
>
> diff --git a/MdeModulePkg/MdeModulePkg.dec b/MdeModulePkg/MdeModulePkg.dec
> index e0ad9373e62f..5220202b233b 100644
> --- a/MdeModulePkg/MdeModulePkg.dec
> +++ b/MdeModulePkg/MdeModulePkg.dec
> @@ -1223,11 +1223,14 @@ [PcdsFixedAtBuild, PcdsPatchableInModule]
> # @Prompt Shadow Peim and PeiCore on boot
> gEfiMdeModulePkgTokenSpaceGuid.PcdShadowPeimOnBoot|TRUE|BOOLEAN|0x30001029
>
> - ## Enable the feature that evacuate temporary memory to permanent memory or not
> + ## Enable the feature that evacuate temporary memory to permanent memory or not<BR><BR>
> # Set FALSE as default, if the developer need this feature to avoid this vulnerability, please
> - # enable it in dsc file.
> - # TRUE - Evacuate temporary memory, the actions include copy memory, convert PPI pointers and so on.
> - # FALSE - Do nothing, for example, no copy memory, no convert PPI pointers and so on.
> + # enable it and disable PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot in dsc file at the same time.<BR>
> + # The reason is that PcdMigrateTemporaryRamFirmwareVolumes will make all PEIMs be shadowed and
> + # it is unnecessary that shadow PEIMs which is controled by PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot
> + # again, it will occupy more memory and waste more time if you enable it.<BR>
> + # TRUE - Evacuate temporary memory, the actions include copy memory, convert PPI pointers and so on.<BR>
> + # FALSE - Do nothing, for example, no copy memory, no convert PPI pointers and so on.<BR>
> # @Prompt Evacuate temporary memory to permanent memory
> gEfiMdeModulePkgTokenSpaceGuid.PcdMigrateTemporaryRamFirmwareVolumes|FALSE|BOOLEAN|0x3000102A
>
So yes, this belongs in patch#1.
The rest of the updates should go into patch#2.
> diff --git a/MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c b/MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c
> index 667d9273bb91..11ff5e693304 100644
> --- a/MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c
> +++ b/MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c
> @@ -1408,7 +1408,11 @@ PeiDispatcher (
> PeimFileHandle = NULL;
> EntryPoint = 0;
>
> - if ((Private->PeiMemoryInstalled) && (Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME || PcdGetBool (PcdShadowPeimOnS3Boot))) {
> + if ((Private->PeiMemoryInstalled) &&
> + (PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)
> + || (Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME)
> + || PcdGetBool (PcdShadowPeimOnS3Boot))
> + ) {
> //
> // Once real memory is available, shadow the RegisterForShadow modules. And meanwhile
> // update the modules' status from PEIM_STATE_REGISTER_FOR_SHADOW to PEIM_STATE_DONE.
(2) The arrangement of the || operators is not idiomatic.
It should be:
if (Private->PeiMemoryInstalled &&
(PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes) ||
Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME ||
PcdGetBool (PcdShadowPeimOnS3Boot))) {
> @@ -1607,13 +1611,17 @@ PeiDispatcher (
> PeiCheckAndSwitchStack (SecCoreData, Private);
>
> if ((Private->PeiMemoryInstalled) && (Private->Fv[FvCount].PeimState[PeimCount] == PEIM_STATE_REGISTER_FOR_SHADOW) && \
> - (Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME || PcdGetBool (PcdShadowPeimOnS3Boot))) {
> + (PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)
> + || (Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME)
> + || PcdGetBool (PcdShadowPeimOnS3Boot))
> + ) {
> //
> // If memory is available we shadow images by default for performance reasons.
> // We call the entry point a 2nd time so the module knows it's shadowed.
> //
> //PERF_START (PeiServices, L"PEIM", PeimFileHandle, 0);
> - if ((Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME) && !PcdGetBool (PcdShadowPeimOnBoot)) {
> + if ((Private->HobList.HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME) && !PcdGetBool (PcdShadowPeimOnBoot)
> + && !PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)) {
> //
> // Load PEIM into Memory for Register for shadow PEIM.
> //
(3) Same as (2) -- for both modifications above --; the operators should
be placed at the ends of the lines.
> diff --git a/MdeModulePkg/Core/Pei/Image/Image.c b/MdeModulePkg/Core/Pei/Image/Image.c
> index 0caeb63e26b4..f9b570ba1f47 100644
> --- a/MdeModulePkg/Core/Pei/Image/Image.c
> +++ b/MdeModulePkg/Core/Pei/Image/Image.c
> @@ -299,7 +299,7 @@ LoadAndRelocatePeCoffImage (
> IsRegisterForShadow = FALSE;
> if ((Private->CurrentFileHandle == FileHandle)
> && (Private->Fv[Private->CurrentPeimFvCount].PeimState[Private->CurrentPeimCount] == PEIM_STATE_REGISTER_FOR_SHADOW)) {
> - IsRegisterForShadow = TRUE;
> + IsRegisterForShadow = TRUE && !PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes);
> }
>
> //
(4) This looks awkward. Consider that
(TRUE && Predicate)
is just
Predicate
So please write
IsRegisterForShadow = !PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes);
> @@ -319,8 +319,7 @@ LoadAndRelocatePeCoffImage (
> // Check whether the file type is PEI module.
> //
> IsPeiModule = FALSE;
> - if (FileInfo.FileType == EFI_FV_FILETYPE_PEI_CORE ||
> - FileInfo.FileType == EFI_FV_FILETYPE_PEIM ||
> + if (FileInfo.FileType == EFI_FV_FILETYPE_PEIM ||
> FileInfo.FileType == EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER) {
> IsPeiModule = TRUE;
> }
> @@ -342,6 +341,7 @@ LoadAndRelocatePeCoffImage (
> // Allocate Memory for the image when memory is ready, and image is relocatable.
> // On normal boot, PcdShadowPeimOnBoot decides whether load PEIM or PeiCore into memory.
> // On S3 boot, PcdShadowPeimOnS3Boot decides whether load PEIM or PeiCore into memory.
> + // PeiCore is specificial case, it will separate from IsPeiModule.
> //
> if ((!ImageContext.RelocationsStripped) && (Private->PeiMemoryInstalled) && ((!IsPeiModule) ||
> (!IsS3Boot && (PcdGetBool (PcdShadowPeimOnBoot) || IsRegisterForShadow)) || (IsS3Boot && PcdGetBool (PcdShadowPeimOnS3Boot)))) {
(5) I don't understand this change.
The LoadAndRelocatePeCoffImage() function is called also when
PcdMigrateTemporaryRamFirmwareVolumes is FALSE; namely from
PeiLoadImageLoadImage().
So this change seems unrelated.
It's possible that this is a fix that's needed separately, for a
pre-existent bug, but then it should get its own dedicated patch.
(Apologies if this change has been introduced since v5 because someone
requested it -- I must have missed the request.)
> diff --git a/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c b/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> index 48605eeada86..3f168bb56893 100644
> --- a/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> +++ b/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> @@ -322,7 +322,8 @@ PeiCore (
> // PEI Core and PEIMs to get high performance.
> //
> OldCoreData->ShadowedPeiCore = (PEICORE_FUNCTION_POINTER) (UINTN) PeiCore;
> - if ((HandoffInformationTable->BootMode == BOOT_ON_S3_RESUME && PcdGetBool (PcdShadowPeimOnS3Boot))
> + if (PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)
> + || (HandoffInformationTable->BootMode == BOOT_ON_S3_RESUME && PcdGetBool (PcdShadowPeimOnS3Boot))
> || (HandoffInformationTable->BootMode != BOOT_ON_S3_RESUME && PcdGetBool (PcdShadowPeimOnBoot))) {
> OldCoreData->ShadowedPeiCore = ShadowPeiCore (OldCoreData);
> }
(6) Same as (2), the operators should be placed at the ends of the
lines.
> @@ -422,10 +423,25 @@ PeiCore (
> }
> } else {
> if (PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)) {
> - if (PrivateData.HobList.HandoffInformationTable->BootMode == BOOT_ON_S3_RESUME) {
> - TempRamEvacuation = PcdGetBool (PcdShadowPeimOnS3Boot);
> - } else {
> - TempRamEvacuation = PcdGetBool (PcdShadowPeimOnBoot);
> + TempRamEvacuation = TRUE;
> +
> + //
> + // When PcdMigrateTemporaryRamFirmwareVolumes is TRUE, it makes sense only
> + // when both PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot is FALSE.
> + // The reason is that PcdMigrateTemporaryRamFirmwareVolumes will make all PEIMs
> + // be shadowed and it is unnecessary that shadow PEIMs which is controled by
> + // PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot again, it will occupy more
> + // memory and waste more time if you enable it.
> + //
> + if (PcdGetBool (PcdShadowPeimOnBoot) || PcdGetBool (PcdShadowPeimOnS3Boot)) {
> + DEBUG ((
> + DEBUG_ERROR,
> + "!!!IMPORTANT NOTICE!!!\n"
> + "When you see the message, it mean that you enable the PcdShadowPeimOnBoot or PcdShadowPeimOnS3Boot when enable PcdMigrateTemporaryRamFirmwareVolumes\n"
> + "It make no sense because it will occupy more memory and waste more time.\n"
> + "You must disable PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot when enable PcdMigrateTemporaryRamFirmwareVolumes for performance reason.\n\n"));
> + ASSERT ((PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes) == TRUE) &&
> + (PcdGetBool (PcdShadowPeimOnBoot) == FALSE) && (PcdGetBool (PcdShadowPeimOnS3Boot) == FALSE));
> }
> }
>
>
(7) This logic change obviates the "TempRamEvacuation" variable. After
this modification, "TempRamEvacuation" stands exactly for
PcdMigrateTemporaryRamFirmwareVolumes, so "TempRamEvacuation" doesn't
need to exist.
Subsequent to the code introduced above, you have the following context:
if (TempRamEvacuation) {
DEBUG ((DEBUG_VERBOSE, "PPI lists before temporary RAM evacuation:\n"));
DumpPpiList (&PrivateData);
//
// Migrate installed content from Temporary RAM to Permanent RAM
//
EvacuateTempRam (&PrivateData, SecCoreData);
DEBUG ((DEBUG_VERBOSE, "PPI lists after temporary RAM evacuation:\n"));
DumpPpiList (&PrivateData);
}
Now that you set TempRamEvacuation to constant TRUE, you end up with a
check like
if (TRUE) {
...
EvacuateTempRam (&PrivateData, SecCoreData);
...
}
So simply remove "TempRamEvacuation" altogether, and *unnest* (fuse) the
code -- the EvacuateTempRam() call -- that depends on
"TempRamEvacuation", into the "if" statement that checks
"PcdMigrateTemporaryRamFirmwareVolumes".
(8) The DEBUG message is superfluous. We already have explanation in the
DEC file, and in a comment just above the ASSERT().
Plus, when the ASSERT() fails, it will also print the condition that
failed -- including the PCD names.
So please drop the DEBUG.
(9) Explicitly comparing BOOLEANs against FALSE or TRUE is bad practice.
PcdGetBool (X) == TRUE
should be replaced with
PcdGetBool (X)
and
PcdGetBool (X) == FALSE
is simply
!PcdGetBool (X).
(10) Checking PcdMigrateTemporaryRamFirmwareVolumes in the ASSERT is
superfluous: you are already in a code block that depends on
PcdMigrateTemporaryRamFirmwareVolumes. See the "if" statement higher up.
(11) When you have:
ASSERT (Cond1 && Cond2);
it is better to write:
ASSERT (Cond1);
ASSERT (Cond2);
Because the behavior is exactly the same, but using separate ASSERT()s
gives more specific information when the original condition fails. The
failure message will report which *sub-condition* fails.
All in all, this is what I propose for fixing points (7) through (11),
expressed here as an incremental patch:
> diff --git a/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c b/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> index 3f168bb56893..2b399e589d85 100644
> --- a/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> +++ b/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c
> @@ -175,11 +175,8 @@ PeiCore (
> EFI_PEI_PCI_CFG2_PPI *PciCfg;
> EFI_HOB_HANDOFF_INFO_TABLE *HandoffInformationTable;
> EFI_PEI_TEMPORARY_RAM_DONE_PPI *TemporaryRamDonePpi;
> UINTN Index;
> - BOOLEAN TempRamEvacuation;
> -
> - TempRamEvacuation = FALSE;
>
> //
> // Retrieve context passed into PEI Core
> //
> @@ -422,31 +419,19 @@ PeiCore (
> ProcessPpiListFromSec ((CONST EFI_PEI_SERVICES **) &PrivateData.Ps, PpiList);
> }
> } else {
> if (PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes)) {
> - TempRamEvacuation = TRUE;
> -
> //
> // When PcdMigrateTemporaryRamFirmwareVolumes is TRUE, it makes sense only
> // when both PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot is FALSE.
> // The reason is that PcdMigrateTemporaryRamFirmwareVolumes will make all PEIMs
> // be shadowed and it is unnecessary that shadow PEIMs which is controled by
> // PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot again, it will occupy more
> // memory and waste more time if you enable it.
> //
> - if (PcdGetBool (PcdShadowPeimOnBoot) || PcdGetBool (PcdShadowPeimOnS3Boot)) {
> - DEBUG ((
> - DEBUG_ERROR,
> - "!!!IMPORTANT NOTICE!!!\n"
> - "When you see the message, it mean that you enable the PcdShadowPeimOnBoot or PcdShadowPeimOnS3Boot when enable PcdMigrateTemporaryRamFirmwareVolumes\n"
> - "It make no sense because it will occupy more memory and waste more time.\n"
> - "You must disable PcdShadowPeimOnBoot and PcdShadowPeimOnS3Boot when enable PcdMigrateTemporaryRamFirmwareVolumes for performance reason.\n\n"));
> - ASSERT ((PcdGetBool (PcdMigrateTemporaryRamFirmwareVolumes) == TRUE) &&
> - (PcdGetBool (PcdShadowPeimOnBoot) == FALSE) && (PcdGetBool (PcdShadowPeimOnS3Boot) == FALSE));
> - }
> - }
> + ASSERT (!PcdGetBool (PcdShadowPeimOnBoot));
> + ASSERT (!PcdGetBool (PcdShadowPeimOnS3Boot));
>
> - if (TempRamEvacuation) {
> DEBUG ((DEBUG_VERBOSE, "PPI lists before temporary RAM evacuation:\n"));
> DumpPpiList (&PrivateData);
>
> //
Thanks
Laszlo
prev parent reply other threads:[~2020-07-22 22:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 8:36 [PATCH v7 00/10] Add new feature that evacuate temporary to permanent memory (CVE-2019-11098) Guomin Jiang
2020-07-22 8:36 ` [PATCH v7 01/10] MdeModulePkg: Add new PCD to control the evacuate temporary memory feature (CVE-2019-11098) Guomin Jiang
2020-07-22 21:19 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 02/10] MdeModulePkg/PeiCore: Enable T-RAM evacuation in PeiCore (CVE-2019-11098) Guomin Jiang
2020-07-22 21:20 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 03/10] UefiCpuPkg/CpuMpPei: Add GDT migration support (CVE-2019-11098) Guomin Jiang
2020-07-22 21:21 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 04/10] UefiCpuPkg/SecMigrationPei: Add initial PEIM (CVE-2019-11098) Guomin Jiang
2020-07-22 16:21 ` [edk2-devel] " Wang, Jian J
2020-07-22 21:24 ` Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 05/10] MdeModulePkg/Core: Create Migrated FV Info Hob for calculating hash (CVE-2019-11098) Guomin Jiang
2020-07-22 21:25 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 06/10] SecurityPkg/Tcg2Pei: Use " Guomin Jiang
2020-07-22 8:36 ` [PATCH v7 07/10] UefiCpuPkg/CpuMpPei: Enable paging and set NP flag to avoid TOCTOU (CVE-2019-11098) Guomin Jiang
2020-07-22 21:29 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 08/10] UefiCpuPkg: Correct some typos Guomin Jiang
2020-07-22 21:30 ` [edk2-devel] " Laszlo Ersek
2020-07-22 8:36 ` [PATCH v7 09/10] SecurityPkg/TcgPei: Use Migrated FV Info Hob for calculating hash (CVE-2019-11098) Guomin Jiang
2020-07-22 8:36 ` [PATCH v7 10/10] MdeModulePkg/Core: Avoid redundant shadow when enable the Migrated PCD (CVE-2019-11098) Guomin Jiang
2020-07-22 22:53 ` Laszlo Ersek [this message]
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=bfbffc42-da7c-e57f-745f-4ffea80530ed@redhat.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