From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mx.groups.io with SMTP id smtpd.web10.2043.1684953564463139142 for ; Wed, 24 May 2023 11:39:24 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20221208 header.b=Nd8a9+ez; spf=pass (domain: gmail.com, ip: 209.85.216.43, mailfrom: kuqin12@gmail.com) Received: by mail-pj1-f43.google.com with SMTP id 98e67ed59e1d1-25394160fd3so422681a91.3 for ; Wed, 24 May 2023 11:39:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684953564; x=1687545564; h=content-transfer-encoding:in-reply-to:content-language:from :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=lRsVF+UTiXfQWne6xbIlpFxKOUaE3OlMIlX0o0V4pIE=; b=Nd8a9+ez6PyvtJOiXTMxvMDmfmqxtHsK7fJ3Lldd8udawEO1k0IcYLbIXuGoHiT9HO VqodaanINIrSCI8A7nx7YPaAkOnsrNM3t6wZ0BJCKa+GOMdzknR1AnghV6gn8kAhL2kk 0/rgc6FQBP0yps3yMYgPNpL5JXeB7dWTVMoyylvd3unz4bsN8bOkdoBFzIJYpeFBsJk4 cb+ZTwSDwVRMe+BG5fq9f6Y0EbY8yAg9j59uMLElnJF20Z5mdH+rHYS6SOs+73flekCe gBYFrXpCnRs6NqgrS1ib+ZH3XQB3nCde/z5OfnrqHGd/0n0OAS/t5PlUSJAoY3T4LdEw o5sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684953564; x=1687545564; h=content-transfer-encoding:in-reply-to:content-language:from :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lRsVF+UTiXfQWne6xbIlpFxKOUaE3OlMIlX0o0V4pIE=; b=MvTRArR10ylPEKDFJb8s7sqFK8quaRQYOqX9n9cwUUgu2/o6MrMWSovePqtdNwW2LS 5Cl4Uo6cyp1ySLimea2qe2Rh7hzU2hXI2/fy5jTpm6W7Dr67lsel950BlpUAVP2ytvTh 96mrsqiSeEdn8dxv8aXvCaTdpRVQu4YXyQckHRRf3LU7lszWMkPHq5eZG5eM2JjP7lMN MLRdOndQ6TuM1iXRvrHzK0kYYPnaneUOPh2/rT35MzK0FQqGtOj4Z0SCOvFHNDZMpjEP r4eMq1nM1TzLT9fWTpOmIn4wE/lTixibfTn3s3nY/8GkeESVfGkcWOyfZAie9D81RqvS ScSw== X-Gm-Message-State: AC+VfDxIW9gb3RM2lh5BlnlOOpzMT4uHEQTgsQWqvgRsYx4DJitJuUgF uPpGRngnOsM+uDjtWOcVdg4q2pqTnvM= X-Google-Smtp-Source: ACHHUZ6DOnGhUpWdWJfqMMj40bTxvKXDMo/AycQahddR87eGgqeUO1udY8I+vLUG5JjK+VITxJ9jfA== X-Received: by 2002:a17:90a:ce01:b0:255:7b0d:9f5d with SMTP id f1-20020a17090ace0100b002557b0d9f5dmr9993641pju.7.1684953563619; Wed, 24 May 2023 11:39:23 -0700 (PDT) Return-Path: Received: from ?IPV6:2001:4898:d8:33:d091:e8e8:7234:655b? ([2001:4898:80e8:b:50a9:e8e8:7234:655b]) by smtp.gmail.com with ESMTPSA id cv6-20020a17090afd0600b0025393752cd5sm3768624pjb.1.2023.05.24.11.39.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 May 2023 11:39:23 -0700 (PDT) Message-ID: Date: Wed, 24 May 2023 11:39:22 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [edk2-devel] [Patch V4 07/15] UefiCpuPkg/PiSmmCpuDxeSmm: Add 2 function to disable/enable CR0.WP To: devel@edk2.groups.io, dun.tan@intel.com Cc: "Dong, Eric" , "Ni, Ray" , "Kumar, Rahul R" , Gerd Hoffmann References: <20230516095932.1525-1-dun.tan@intel.com> <20230516095932.1525-8-dun.tan@intel.com> <88ebdba4-c595-2b4e-885e-a0fef4beea2f@gmail.com> From: "Kun Qin" In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Dun, Thanks for your reply. That was helpful! Just a follow-up question, is there any plan to support heap guard with PcdCpuSmmRestrictedMemoryAccess enabled after these changes? I think it would be a great value prop for the developers to have both features enabled during firmware validation process. Thanks, Kun On 5/23/2023 2:14 AM, duntan wrote: > Hi Kun, > > I've updated my answers in your original mail. > > Thanks, > Dun > > -----Original Message----- > From: Kun Qin > Sent: Saturday, May 20, 2023 10:00 AM > To: devel@edk2.groups.io; Tan, Dun > Cc: Dong, Eric ; Ni, Ray ; Kumar, Rahul R ; Gerd Hoffmann > Subject: Re: [edk2-devel] [Patch V4 07/15] UefiCpuPkg/PiSmmCpuDxeSmm: Add 2 function to disable/enable CR0.WP > > Hi Dun, > > Thanks for the notice on the other thread (v4 04/15). > > I have a few more questions on this specific patch (and a few associated commits related to it): > > Why would we allow page table manipulation after `mIsReadOnlyPageTable` is evaluated to TRUE? > Dun: `mIsReadOnlyPageTable` is a flag to indicate that current page table has been marked as RO and the new allocated pool should also be RO. We only need to clear Cr0.WP before modify page table. > > > As far as I can tell, `mIsReadOnlyPageTable` is set to TRUE inside `SetPageTableAttributes` function, but then we also have code in `InitializePageTablePool` to expect more page tables to be allocated. > Could you please let me when this would happen? > Dun: After `SetPageTableAttributes`, in 'SmmCpuFeaturesCompleteSmmReadyToLock()' API of different platform SmmCpuFeaturesLib, EDKII_SMM_MEMORY_ATTRIBUTE_PROTOCOL may be used to convert memory attribute. Also, in SMI handler after ReadyToLock, EDKII_SMM_MEMORY_ATTRIBUTE_PROTOCOL still may be used to convert memory attribute. During this process, if page split happens, new page table pool may be allocated. > > > I thought there would not be any new page table memory (i.e. memory attribute update) after ready to lock with restricted memory access option? With these change, it seems to be doable through EDKII_SMM_MEMORY_ATTRIBUTE_PROTOCOL now, is that correct? If so, would you mind shedding some light on what other behavior changes there might be? > Dun: Do you mean that we should check if ReadyToLock in EDKII_SMM_MEMORY_ATTRIBUTE_PROTOCOL implementation to make sure that page table won't be modified after ReadyToLock? > If is, as I mentioned above, page table still may be modified after ReadyToLock. > > > In addition, I might miss it in the patch series. If the newly allocated page memory is marked as read only after the above flag is set to TRUE, how would the callers able to use them? > Dun: Caller can clear the Cr0.WP before modifying the page table. > > > Thanks in advance. > > Regards, > Kun > > On 5/16/2023 2:59 AM, duntan wrote: >> Add two functions to disable/enable CR0.WP. These two unctions will >> also be used in later commits. This commit doesn't change any >> functionality. >> >> Signed-off-by: Dun Tan >> Cc: Eric Dong >> Cc: Ray Ni >> Cc: Rahul Kumar >> Cc: Gerd Hoffmann >> --- >> UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 24 ++++++++++++++++++++++++ >> UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------- >> 2 files changed, 90 insertions(+), 49 deletions(-) >> >> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h >> b/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h >> index ba341cadc6..e0c4ca76dc 100644 >> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h >> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h >> @@ -1565,4 +1565,28 @@ SmmWaitForApArrival ( >> VOID >> ); >> >> +/** >> + Disable Write Protect on pages marked as read-only if Cr0.Bits.WP is 1. >> + >> + @param[out] WpEnabled If Cr0.WP is enabled. >> + @param[out] CetEnabled If CET is enabled. >> +**/ >> +VOID >> +DisableReadOnlyPageWriteProtect ( >> + OUT BOOLEAN *WpEnabled, >> + OUT BOOLEAN *CetEnabled >> + ); >> + >> +/** >> + Enable Write Protect on pages marked as read-only. >> + >> + @param[out] WpEnabled If Cr0.WP should be enabled. >> + @param[out] CetEnabled If CET should be enabled. >> +**/ >> +VOID >> +EnableReadOnlyPageWriteProtect ( >> + BOOLEAN WpEnabled, >> + BOOLEAN CetEnabled >> + ); >> + >> #endif >> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c >> b/UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c >> index 2faee8f859..4b512edf68 100644 >> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c >> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c >> @@ -40,6 +40,64 @@ PAGE_TABLE_POOL *mPageTablePool = NULL; >> // >> BOOLEAN mIsReadOnlyPageTable = FALSE; >> >> +/** >> + Disable Write Protect on pages marked as read-only if Cr0.Bits.WP is 1. >> + >> + @param[out] WpEnabled If Cr0.WP is enabled. >> + @param[out] CetEnabled If CET is enabled. >> +**/ >> +VOID >> +DisableReadOnlyPageWriteProtect ( >> + OUT BOOLEAN *WpEnabled, >> + OUT BOOLEAN *CetEnabled >> + ) >> +{ >> + IA32_CR0 Cr0; >> + >> + *CetEnabled = ((AsmReadCr4 () & CR4_CET_ENABLE) != 0) ? TRUE : FALSE; >> + Cr0.UintN = AsmReadCr0 (); >> + *WpEnabled = (Cr0.Bits.WP != 0) ? TRUE : FALSE; if (*WpEnabled) { >> + if (*CetEnabled) { >> + // >> + // CET must be disabled if WP is disabled. Disable CET before clearing CR0.WP. >> + // >> + DisableCet (); >> + } >> + >> + Cr0.Bits.WP = 0; >> + AsmWriteCr0 (Cr0.UintN); >> + } >> +} >> + >> +/** >> + Enable Write Protect on pages marked as read-only. >> + >> + @param[out] WpEnabled If Cr0.WP should be enabled. >> + @param[out] CetEnabled If CET should be enabled. >> +**/ >> +VOID >> +EnableReadOnlyPageWriteProtect ( >> + BOOLEAN WpEnabled, >> + BOOLEAN CetEnabled >> + ) >> +{ >> + IA32_CR0 Cr0; >> + >> + if (WpEnabled) { >> + Cr0.UintN = AsmReadCr0 (); >> + Cr0.Bits.WP = 1; >> + AsmWriteCr0 (Cr0.UintN); >> + >> + if (CetEnabled) { >> + // >> + // re-enable CET. >> + // >> + EnableCet (); >> + } >> + } >> +} >> + >> /** >> Initialize a buffer pool for page table use only. >> >> @@ -62,10 +120,9 @@ InitializePageTablePool ( >> IN UINTN PoolPages >> ) >> { >> - VOID *Buffer; >> - BOOLEAN CetEnabled; >> - BOOLEAN WpEnabled; >> - IA32_CR0 Cr0; >> + VOID *Buffer; >> + BOOLEAN WpEnabled; >> + BOOLEAN CetEnabled; >> >> // >> // Always reserve at least PAGE_TABLE_POOL_UNIT_PAGES, including >> one page for @@ -102,34 +159,9 @@ InitializePageTablePool ( >> // If page table memory has been marked as RO, mark the new pool pages as read-only. >> // >> if (mIsReadOnlyPageTable) { >> - CetEnabled = ((AsmReadCr4 () & CR4_CET_ENABLE) != 0) ? TRUE : FALSE; >> - Cr0.UintN = AsmReadCr0 (); >> - WpEnabled = (Cr0.Bits.WP != 0) ? TRUE : FALSE; >> - if (WpEnabled) { >> - if (CetEnabled) { >> - // >> - // CET must be disabled if WP is disabled. Disable CET before clearing CR0.WP. >> - // >> - DisableCet (); >> - } >> - >> - Cr0.Bits.WP = 0; >> - AsmWriteCr0 (Cr0.UintN); >> - } >> - >> + DisableReadOnlyPageWriteProtect (&WpEnabled, &CetEnabled); >> SmmSetMemoryAttributes ((EFI_PHYSICAL_ADDRESS)(UINTN)Buffer, EFI_PAGES_TO_SIZE (PoolPages), EFI_MEMORY_RO); >> - if (WpEnabled) { >> - Cr0.UintN = AsmReadCr0 (); >> - Cr0.Bits.WP = 1; >> - AsmWriteCr0 (Cr0.UintN); >> - >> - if (CetEnabled) { >> - // >> - // re-enable CET. >> - // >> - EnableCet (); >> - } >> - } >> + EnableReadOnlyPageWriteProtect (WpEnabled, CetEnabled); >> } >> >> return TRUE; >> @@ -1782,6 +1814,7 @@ SetPageTableAttributes ( >> VOID >> ) >> { >> + BOOLEAN WpEnabled; >> BOOLEAN CetEnabled; >> >> if (!IfReadOnlyPageTableNeeded ()) { @@ -1794,15 +1827,7 @@ >> SetPageTableAttributes ( >> // Disable write protection, because we need mark page table to be write protected. >> // We need *write* page table memory, to mark itself to be *read only*. >> // >> - CetEnabled = ((AsmReadCr4 () & CR4_CET_ENABLE) != 0) ? TRUE : >> FALSE; >> - if (CetEnabled) { >> - // >> - // CET must be disabled if WP is disabled. >> - // >> - DisableCet (); >> - } >> - >> - AsmWriteCr0 (AsmReadCr0 () & ~CR0_WP); >> + DisableReadOnlyPageWriteProtect (&WpEnabled, &CetEnabled); >> >> // Set memory used by page table as Read Only. >> DEBUG ((DEBUG_INFO, "Start...\n")); @@ -1811,20 +1836,12 @@ >> SetPageTableAttributes ( >> // >> // Enable write protection, after page table attribute updated. >> // >> - AsmWriteCr0 (AsmReadCr0 () | CR0_WP); >> + EnableReadOnlyPageWriteProtect (TRUE, CetEnabled); >> mIsReadOnlyPageTable = TRUE; >> >> // >> // Flush TLB after mark all page table pool as read only. >> // >> FlushTlbForAll (); >> - >> - if (CetEnabled) { >> - // >> - // re-enable CET. >> - // >> - EnableCet (); >> - } >> - >> return; >> } > > > >