public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: "Kubacki, Michael A" <michael.a.kubacki@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Chaganty, Rangasai V" <rangasai.v.chaganty@intel.com>
Subject: Re: [edk2-platforms][PATCH V1 1/1] IntelSiliconPkg/IntelVTdDxe: Fix NULL pointer dereference
Date: Mon, 26 Aug 2019 23:51:59 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C29CD54@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190824025411.1192-1-michael.a.kubacki@intel.com>

Michael,


> -----Original Message-----
> From: Kubacki, Michael A
> Sent: Friday, August 23, 2019 7:54 PM
> To: devel@edk2.groups.io
> Cc: Ni, Ray <ray.ni@intel.com>; Chaganty, Rangasai V <rangasai.v.chaganty@intel.com>
> Subject: [edk2-platforms][PATCH V1 1/1] IntelSiliconPkg/IntelVTdDxe: Fix NULL pointer dereference
> 
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2116
> 
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Rangasai V Chaganty <rangasai.v.chaganty@intel.com>
> Signed-off-by: Michael Kubacki <michael.a.kubacki@intel.com>
> ---
>  Silicon/Intel/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c | 19 +++++++++++--------
>  1 file changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git a/Silicon/Intel/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> b/Silicon/Intel/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> index 956ebb2d3d..9b6135ef94 100644
> --- a/Silicon/Intel/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> +++ b/Silicon/Intel/IntelSiliconPkg/Feature/VTd/IntelVTdDxe/DmaProtection.c
> @@ -158,10 +158,13 @@ ProcessRequestedAccessAttribute (
>  }
> 
>  /**
> -  return the UEFI memory information.
> +  Return UEFI memory map information.
> +
> +  @param[out] Below4GMemoryLimit  The below 4GiB memory limit address or 0 if insufficient resources exist to
> +                                  determine the address.
> +  @param[out] Above4GMemoryLimit  The above 4GiB memory limit address or 0 if insufficient resources exist to
> +                                  determine the address.
> 
> -  @param[out] Below4GMemoryLimit  The below 4GiB memory limit
> -  @param[out] Above4GMemoryLimit  The above 4GiB memory limit
>  **/
>  VOID
>  ReturnUefiMemoryMap (
> @@ -206,7 +209,11 @@ ReturnUefiMemoryMap (
>      // we process bogus entries and create bogus E820 entries.
>      //
>      EfiMemoryMap = (EFI_MEMORY_DESCRIPTOR *) AllocatePool (EfiMemoryMapSize);
> -    ASSERT (EfiMemoryMap != NULL);
> +    if (EfiMemoryMap == NULL) {
> +      ASSERT (EfiMemoryMap != NULL);

Above line may trigger a unreachable code error from some static code scanner.
How about move assertion to the line before if?

> +      return;
> +    }
> +
>      Status = gBS->GetMemoryMap (
>                      &EfiMemoryMapSize,
>                      EfiMemoryMap,
> @@ -218,7 +225,6 @@ ReturnUefiMemoryMap (
>        FreePool (EfiMemoryMap);
>      }
>    } while (Status == EFI_BUFFER_TOO_SMALL);
> -
>    ASSERT_EFI_ERROR (Status);
> 
>    //
> @@ -242,9 +248,6 @@ ReturnUefiMemoryMap (
>      NextEfiEntry  = NEXT_MEMORY_DESCRIPTOR (EfiEntry, EfiDescriptorSize);
>    }
> 
> -  //
> -  //
> -  //
>    DEBUG ((DEBUG_INFO, "MemoryMap:\n"));
>    EfiEntry        = EfiMemoryMap;
>    EfiMemoryMapEnd = (EFI_MEMORY_DESCRIPTOR *) ((UINT8 *) EfiMemoryMap + EfiMemoryMapSize);
> --
> 2.16.2.windows.1


  parent reply	other threads:[~2019-08-26 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24  2:54 [edk2-platforms][PATCH V1 1/1] IntelSiliconPkg/IntelVTdDxe: Fix NULL pointer dereference Kubacki, Michael A
2019-08-26 23:41 ` Chaganty, Rangasai V
2019-08-26 23:51 ` Ni, Ray [this message]
2019-08-27  0:47   ` Ni, Ray

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=734D49CCEBEEF84792F5B80ED585239D5C29CD54@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