public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Jian J Wang <jian.j.wang@intel.com>
Cc: edk2-devel@lists.01.org, Ruiyu Ni <ruiyu.ni@intel.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Star Zeng <star.zeng@intel.com>
Subject: Re: [PATCH 2/2] MdeModulePkg/Core: fix ineffective guard page issue
Date: Tue, 6 Nov 2018 12:09:37 +0000	[thread overview]
Message-ID: <20181106120937.3k73y7l6ucsqxil6@bivouac.eciton.net> (raw)
In-Reply-To: <20181103064221.4764-3-jian.j.wang@intel.com>

On Sat, Nov 03, 2018 at 02:42:21PM +0800, Jian J Wang wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1295
> 
> This issue originates from following patch which allows to enable
> paging if PcdImageProtectionPolicy and PcdDxeNxMemoryProtectionPolicy
> (in addition to PcdSetNxForStack) are set to enable related features.
> 
>   5267926134d17e86672b84fd57b438f05ffa68e1
> 
> Due to above change, PcdImageProtectionPolicy will be set to 0 by
> default in many platforms, which, in turn, cause following code in
> MdeModulePkg\Core\Dxe\Misc\MemoryProtection.c fail the creation of
> notify event of CpuArchProtocol.
> 
> 1138:  if (mImageProtectionPolicy != 0 ||
>            PcdGet64 (PcdDxeNxMemoryProtectionPolicy) != 0) {
> 1139:  Status = CoreCreateEvent (
> ...
> 1142:             MemoryProtectionCpuArchProtocolNotify,
> ...
> 1145:             );
> 
> Then following call flow won't be done and Guard pages will not be
> set as not-present in SetAllGuardPages() eventually.
> 
>    MemoryProtectionCpuArchProtocolNotify()
> => HeapGuardCpuArchProtocolNotify()
> => SetAllGuardPages()
> 
> The solution is removing the if(...) statement so that the notify
> event will always be created and handler be registered. This won't
> cause unnecessary code execution because, in the notify event handler,
> the related PCDs like
> 
>     PcdImageProtectionPolicy and
>     PcdDxeNxMemoryProtectionPolicy
> 
> will be checked again to do its job.
> 
> Cc: Star Zeng <star.zeng@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 | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> index 30e5c5153c..30798b05b9 100644
> --- a/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> +++ b/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c
> @@ -1135,7 +1135,6 @@ CoreInitializeMemoryProtection (
>    ASSERT (GetPermissionAttributeForMemoryType (EfiBootServicesData) ==
>            GetPermissionAttributeForMemoryType (EfiConventionalMemory));
>  
> -  if (mImageProtectionPolicy != 0 || PcdGet64 (PcdDxeNxMemoryProtectionPolicy) != 0) {
>    Status = CoreCreateEvent (
>               EVT_NOTIFY_SIGNAL,
>               TPL_CALLBACK,
> @@ -1154,7 +1153,6 @@ CoreInitializeMemoryProtection (
>               &Registration
>               );
>    ASSERT_EFI_ERROR(Status);
> -  }

And here we see why.
The indentation changes need to be part of this patch, not 1/2.

/
    Leif

>  
>    //
>    // Register a callback to disable NULL pointer detection at EndOfDxe
> -- 
> 2.16.2.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-11-06 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03  6:42 [PATCH 0/2] fix ineffective guard page issue Jian J Wang
2018-11-03  6:42 ` [PATCH 1/2] MdeModulePkg/Core: fill logic hole in MemoryProtectionCpuArchProtocolNotify Jian J Wang
2018-11-06 12:07   ` Leif Lindholm
2018-11-03  6:42 ` [PATCH 2/2] MdeModulePkg/Core: fix ineffective guard page issue Jian J Wang
2018-11-06 12:09   ` Leif Lindholm [this message]
2018-11-07  0:38     ` 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=20181106120937.3k73y7l6ucsqxil6@bivouac.eciton.net \
    --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