public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Wang, Jian J" <jian.j.wang@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] Enable page table write protection
Date: Wed, 29 Nov 2017 10:56:04 +0000	[thread overview]
Message-ID: <47960CCE-CA63-49FE-99AF-48E61050EF05@intel.com> (raw)
In-Reply-To: <D827630B58408649ACB04F44C510003624CB8852@SHSMSX103.ccr.corp.intel.com>

Is this code in CPU driver?

thank you!
Yao, Jiewen


> 在 2017年11月29日,下午6:24,Wang, Jian J <jian.j.wang@intel.com> 写道:
> 
> Yes, I validated them manually with JTAG debug tool. 
> 
> if ((L3PageTable[Index3] & IA32_PG_PS) != 0) {
>   // 1G page. Split to 2M.
>   L2PageTable = AllocatePages (1);
>   ASSERT (L2PageTable != NULL);
>    PhysicalAddress = L3PageTable[Index3] & PAGING_1G_ADDRESS_MASK_64;
>    for (Index = 0; Index < EFI_PAGE_SIZE/sizeof (UINT64); ++Index) {
>     L2PageTable[Index] = PhysicalAddress  | AddressEncMask |
>                          IA32_PG_PS | IA32_PG_P | IA32_PG_RW;
>     PhysicalAddress += SIZE_2MB;
>   }
>   L3PageTable[Index3] = (UINT64) (UINTN) L2PageTable | AddressEncMask |
>                                          IA32_PG_P | IA32_PG_RW;
>   SetPageReadOnly (PageTableBase, (EFI_PHYSICAL_ADDRESS)(UINTN)L2PageTable);
> }
> 
> The newly allocated page table is set in the SetPageReadOnly() itself recursively, like
> above code in which L2PageTable is allocated and then set it to be read-only after
> initializing the table content.
> 
>> -----Original Message-----
>> From: Yao, Jiewen
>> Sent: Wednesday, November 29, 2017 5:16 PM
>> To: Wang, Jian J <jian.j.wang@intel.com>
>> Cc: edk2-devel@lists.01.org
>> Subject: Re: [edk2] [PATCH 0/2] Enable page table write protection
>> 
>> Thanks.
>> 
>> May I know if this is validated in uefi shell, that all page table is readonly?
>> 
>> I did not find the code to set new allocated split page to be readonly. Can you
>> give me a hand on that?
>> 
>> thank you!
>> Yao, Jiewen
>> 
>> 
>>> 在 2017年11月29日,下午4:47,Jian J Wang <jian.j.wang@intel.com> 写
>> 道:
>>> 
>>> Write Protect feature (CR0.WP) is always enabled in driver
>> UefiCpuPkg/CpuDxe.
>>> But the memory pages used for page table are not set as read-only in the
>> driver
>>> DxeIplPeim, after the paging is setup. This might jeopardize the page table
>>> integrity if there's buffer overflow occured in other part of system.
>>> 
>>> This patch series will change this situation by clearing R/W bit in page attribute
>>> of the pages used as page table.
>>> 
>>> Validation works include booting Windows (10/server 2016) and Linux
>> (Fedora/Ubuntu)
>>> on OVMF and Intel real platform.
>>> 
>>> Jian J Wang (2):
>>> UefiCpuPkg/CpuDxe: Check CR0.WP before changing page table
>>> MdeModulePkg/DxeIpl: Mark page table as read-only
>>> 
>>> MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c | 166
>> +++++++++++++++++++++++
>>> MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.h |  14 ++
>>> UefiCpuPkg/CpuDxe/CpuPageTable.c                 |  65 ++++++++-
>>> 3 files changed, 241 insertions(+), 4 deletions(-)
>>> 
>>> --
>>> 2.14.1.windows.1
>>> 
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel

  reply	other threads:[~2017-11-29 10:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  8:46 [PATCH 0/2] Enable page table write protection Jian J Wang
2017-11-29  8:46 ` [PATCH 1/2] UefiCpuPkg/CpuDxe: Check CR0.WP before changing page table Jian J Wang
2017-11-29  8:46 ` [PATCH 2/2] MdeModulePkg/DxeIpl: Mark page table as read-only Jian J Wang
2017-11-29  9:15 ` [PATCH 0/2] Enable page table write protection Yao, Jiewen
2017-11-29 10:24   ` Wang, Jian J
2017-11-29 10:56     ` Yao, Jiewen [this message]
2017-11-29 12:15       ` Wang, Jian J
2017-11-29 13:35         ` Yao, Jiewen
2017-11-30  0:44           ` Wang, Jian J
2017-11-30  0:51             ` Yao, Jiewen
2017-11-30  1:16               ` Wang, Jian J
2017-11-30  1:36                 ` Yao, Jiewen
2017-11-30  1:43                   ` Yao, Jiewen
2017-11-30  1:46                   ` Wang, Jian J
2017-11-30  1:59                     ` Yao, Jiewen
2017-11-30  2:02                       ` Wang, Jian J
2017-11-30  2:36                       ` Wang, Jian J
2017-11-30  1:37                 ` Andrew Fish
2017-11-30  1:52                   ` Wang, Jian J
2017-11-29 12:38 ` Laszlo Ersek
2017-11-29 12:46   ` Wang, Jian J

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=47960CCE-CA63-49FE-99AF-48E61050EF05@intel.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