From: Hao Wu <hao.a.wu@intel.com>
To: edk2-devel@lists.01.org
Cc: Hao Wu <hao.a.wu@intel.com>, Jian J Wang <jian.j.wang@intel.com>,
Star Zeng <star.zeng@intel.com>, Eric Dong <eric.dong@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>, Ruiyu Ni <ruiyu.ni@intel.com>
Subject: [PATCH v2 0/2] Resolve feature conflict between NX and Stack guard
Date: Tue, 6 Mar 2018 21:33:01 +0800 [thread overview]
Message-ID: <20180306133303.14772-1-hao.a.wu@intel.com> (raw)
V2 changes:
A. Use Hoblib APIs to get the base of stack from Hob.
B. Remove unnecessary local variable used in function
InitializeDxeNxMemoryProtectionPolicy().
V1 history:
If enabled, NX memory protection feature will mark some types of active
memory as NX (non-executable), which includes the first page of the stack.
This will overwrite the attributes of the first page of the stack if the
stack guard feature is also enabled.
The series will override the attributes setting to the first page of the
stack by adding back the 'EFI_MEMORY_RP' attribute when the stack guard
feature is enabled.
Cc: Jian J Wang <jian.j.wang@intel.com>
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>
Hao Wu (2):
MdeModulePkg/Core: Refine handling NULL detection in NX setting
MdeModulePkg/Core: Fix feature conflict between NX and Stack guard
MdeModulePkg/Core/Dxe/DxeMain.inf | 4 +-
MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c | 74 +++++++++++++++++++++++----
2 files changed, 67 insertions(+), 11 deletions(-)
--
2.12.0.windows.1
next reply other threads:[~2018-03-06 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:33 Hao Wu [this message]
2018-03-06 13:33 ` [PATCH v2 1/2] MdeModulePkg/Core: Refine handling NULL detection in NX setting Hao Wu
2018-03-06 13:33 ` [PATCH v2 2/2] MdeModulePkg/Core: Fix feature conflict between NX and Stack guard Hao Wu
2018-03-06 13:38 ` Yao, Jiewen
2018-03-07 1:50 ` [PATCH v2 0/2] Resolve " Wang, Jian J
2018-03-07 3:16 ` Ni, Ruiyu
2018-03-07 3:39 ` Wang, Jian J
2018-03-07 4:13 ` Yao, Jiewen
2018-03-07 4:28 ` Wu, Hao A
2018-03-07 4:32 ` Ni, Ruiyu
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=20180306133303.14772-1-hao.a.wu@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