From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: Jian J Wang <jian.j.wang@intel.com>, edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>, Eric Dong <eric.dong@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [PATCH] MdeModulePkg/Core: fix feature conflict between NX and NULL detection
Date: Tue, 30 Jan 2018 12:38:11 +0800 [thread overview]
Message-ID: <eb757e29-56ee-b37c-3e07-9f7433e8f1e6@Intel.com> (raw)
In-Reply-To: <20180129110950.24212-1-jian.j.wang@intel.com>
On 1/29/2018 7:09 PM, Jian J Wang wrote:
> If enabled, NX memory protection feature will mark all free memory as
> NX (non-executable), including page 0. This will overwrite the attributes
> of page 0 if NULL pointer detection feature is also enabled and then
> compromise the functionality of it. The solution is skipping the NX
> attributes setting to page 0 if NULL pointer detection feature is enabled.
>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
> ---
> MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> index 862593f562..150167bf66 100644
> --- a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> +++ b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> @@ -845,10 +845,22 @@ InitializeDxeNxMemoryProtectionPolicy (
>
> Attributes = GetPermissionAttributeForMemoryType (MemoryMapEntry->Type);
> if (Attributes != 0) {
> - SetUefiImageMemoryAttributes (
> - MemoryMapEntry->PhysicalStart,
> - LShiftU64 (MemoryMapEntry->NumberOfPages, EFI_PAGE_SHIFT),
> - Attributes);
> + if (MemoryMapEntry->PhysicalStart == 0 &&
> + PcdGet8 (PcdNullPointerDetectionPropertyMask) != 0) {
> + //
> + // Skip page 0 if NULL pointer detection is enabled to avoid attributes
> + // overwritten.
> + //
> + SetUefiImageMemoryAttributes (
> + MemoryMapEntry->PhysicalStart + EFI_PAGE_SIZE,
> + LShiftU64 (MemoryMapEntry->NumberOfPages - 1, EFI_PAGE_SHIFT),
> + Attributes);
> + } else {
> + SetUefiImageMemoryAttributes (
> + MemoryMapEntry->PhysicalStart,
> + LShiftU64 (MemoryMapEntry->NumberOfPages, EFI_PAGE_SHIFT),
> + Attributes);
> + }
> }
> MemoryMapEntry = NEXT_MEMORY_DESCRIPTOR (MemoryMapEntry, DescriptorSize);
> }
>
Does this bug expose an API-level issue?
SetUefiImageMemoryAttributes () should also accept a Mask value?
--
Thanks,
Ray
next prev parent reply other threads:[~2018-01-30 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 11:09 [PATCH] MdeModulePkg/Core: fix feature conflict between NX and NULL detection Jian J Wang
2018-01-30 2:09 ` Yao, Jiewen
2018-02-01 1:14 ` Wang, Jian J
2018-01-30 4:38 ` Ni, Ruiyu [this message]
2018-02-01 1:17 ` Wang, Jian J
2018-02-01 5:33 ` Ni, Ruiyu
2018-02-01 5:54 ` Ni, Ruiyu
2018-02-01 5:59 ` 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=eb757e29-56ee-b37c-3e07-9f7433e8f1e6@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