public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Fan, Jeff" <jeff.fan@intel.com>, "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH] MdeModulePkg VariableSmm: Do not need check CommBufferSize buffer
Date: Mon, 12 Dec 2016 01:10:18 +0000	[thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503A8B9898@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103B7AA442@SHSMSX104.ccr.corp.intel.com>

Reviewed-by: Jiewen.yao@intel.com


> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Star
> Zeng
> Sent: Friday, December 9, 2016 2:53 PM
> To: edk2-devel@lists.01.org
> Cc: Yao, Jiewen <jiewen.yao@intel.com>; Fan, Jeff <jeff.fan@intel.com>; Zeng,
> Star <star.zeng@intel.com>
> Subject: [edk2] [PATCH] MdeModulePkg VariableSmm: Do not need check
> CommBufferSize buffer
> 
> Current code in SmmVariableHandler() checks CommBufferSize buffer to make
> sure it points to outside SMRAM in "case
> SMM_VARIABLE_FUNCTION_GET_STATISTICS".
> 
> But after eaae7b33b1cf6b9f21db1636f219c2b6a8d88afd,
> CommBufferSize buffer points to SMRAM that was used by SMM core to cache
> CommSize from SmmCommunication protocol, then the check will fail definitely
> and GET_STATISTICS feature breaks.
> 
> In fact, do not need check CommBufferSize buffer at all even before
> eaae7b33b1cf6b9f21db1636f219c2b6a8d88afd.
> Before eaae7b33b1cf6b9f21db1636f219c2b6a8d88afd,
> CommBufferSize buffer pointed to gSmmCorePrivate->BufferSize that is outside
> SMRAM, the check will success definitely; after
> eaae7b33b1cf6b9f21db1636f219c2b6a8d88afd,
> CommBufferSize buffer points to local variable BufferSize (in SMRAM) in
> SmmEntryPoint(), the check is not needed definitely.
> 
> The patch is to remove the check.
> 
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jeff Fan <jeff.fan@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
>  MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.c | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.c
> b/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.c
> index eafb53322e8c..c714916019ef 100644
> --- a/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.c
> +++ b/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.c
> @@ -695,11 +695,10 @@ SmmVariableHandler (
>        // It is covered by previous CommBuffer check
>        //
> 
> -      if (!SmmIsBufferOutsideSmmValid
> ((EFI_PHYSICAL_ADDRESS)(UINTN)CommBufferSize, sizeof(UINTN))) {
> -        DEBUG ((EFI_D_ERROR, "GetStatistics: SMM communication buffer in
> SMRAM!\n"));
> -        Status = EFI_ACCESS_DENIED;
> -        goto EXIT;
> -      }
> +      //
> +      // Do not need to check CommBufferSize buffer as it should point to
> SMRAM
> +      // that was used by SMM core to cache CommSize from
> SmmCommunication protocol.
> +      //
> 
>        Status = SmmVariableGetStatistics (VariableInfo, &InfoSize);
>        *CommBufferSize = InfoSize +
> SMM_VARIABLE_COMMUNICATE_HEADER_SIZE;
> --
> 2.7.0.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2016-12-12  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  6:53 [PATCH] MdeModulePkg VariableSmm: Do not need check CommBufferSize buffer Star Zeng
     [not found] ` <0C09AFA07DD0434D9E2A0C6AEB0483103B7AA442@SHSMSX104.ccr.corp.intel.com>
2016-12-12  1:10   ` Yao, Jiewen [this message]

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=74D8A39837DF1E4DA445A8C0B3885C503A8B9898@SHSMSX104.ccr.corp.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