From: "Gao, Liming" <liming.gao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Michael Turner <Michael.Turner@microsoft.com>
Subject: Re: [PATCH] MdePkg DxeServicesLib: Handle potential NULL FvHandle
Date: Fri, 5 May 2017 09:10:29 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D72A993@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1493972489-55348-1-git-send-email-star.zeng@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: Zeng, Star
>Sent: Friday, May 05, 2017 4:21 PM
>To: edk2-devel@lists.01.org
>Cc: Zeng, Star <star.zeng@intel.com>; Gao, Liming <liming.gao@intel.com>;
>Kinney, Michael D <michael.d.kinney@intel.com>; Michael Turner
><Michael.Turner@microsoft.com>
>Subject: [PATCH] MdePkg DxeServicesLib: Handle potential NULL FvHandle
>
>REF: https://bugzilla.tianocore.org/show_bug.cgi?id=514
>
>The FvHandle input to InternalGetSectionFromFv() may be NULL,
>then ASSERT will appear. It is because the LoadedImage->DeviceHandle
>returned from InternalImageHandleToFvHandle() may be NULL.
>For example for DxeCore, there is LoadedImage protocol installed
>for it, but the LoadedImage->DeviceHandle could not be initialized
>before the FV2 (contain DxeCore) protocol is installed.
>
>This patch is to update InternalGetSectionFromFv() to return
>EFI_NOT_FOUND directly for NULL FvHandle.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Michael Kinney <michael.d.kinney@intel.com>
>Cc: Michael Turner <Michael.Turner@microsoft.com>
>Contributed-under: TianoCore Contribution Agreement 1.0
>Signed-off-by: Star Zeng <star.zeng@intel.com>
>---
> MdePkg/Library/DxeServicesLib/DxeServicesLib.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
>diff --git a/MdePkg/Library/DxeServicesLib/DxeServicesLib.c
>b/MdePkg/Library/DxeServicesLib/DxeServicesLib.c
>index 2adf76fd8d22..1827c9216fbc 100644
>--- a/MdePkg/Library/DxeServicesLib/DxeServicesLib.c
>+++ b/MdePkg/Library/DxeServicesLib/DxeServicesLib.c
>@@ -2,7 +2,7 @@
> MDE DXE Services Library provides functions that simplify the development
>of DXE Drivers.
> These functions help access data from sections of FFS files or from file path.
>
>- Copyright (c) 2007 - 2015, Intel Corporation. All rights reserved.<BR>
>+ Copyright (c) 2007 - 2017, Intel Corporation. All rights reserved.<BR>
> (C) Copyright 2015 Hewlett Packard Enterprise Development LP<BR>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions of the BSD
>License
>@@ -62,6 +62,12 @@ InternalImageHandleToFvHandle (
>
> ASSERT_EFI_ERROR (Status);
>
>+ //
>+ // The LoadedImage->DeviceHandle may be NULL.
>+ // For example for DxeCore, there is LoadedImage protocol installed for it,
>but the
>+ // LoadedImage->DeviceHandle could not be initialized before the FV2
>(contain DxeCore)
>+ // protocol is installed.
>+ //
> return LoadedImage->DeviceHandle;
>
> }
>@@ -84,7 +90,6 @@ InternalImageHandleToFvHandle (
> The data and size is returned by Buffer and Size. The caller is responsible to
>free the Buffer allocated
> by this function. This function can be only called at TPL_NOTIFY and below.
>
>- If FvHandle is NULL, then ASSERT ();
> If NameGuid is NULL, then ASSERT();
> If Buffer is NULL, then ASSERT();
> If Size is NULL, then ASSERT().
>@@ -128,7 +133,12 @@ InternalGetSectionFromFv (
> ASSERT (Buffer != NULL);
> ASSERT (Size != NULL);
>
>- ASSERT (FvHandle != NULL);
>+ if (FvHandle == NULL) {
>+ //
>+ // Return EFI_NOT_FOUND directly for NULL FvHandle.
>+ //
>+ return EFI_NOT_FOUND;
>+ }
>
> Status = gBS->HandleProtocol (
> FvHandle,
>--
>2.7.0.windows.1
prev parent reply other threads:[~2017-05-05 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 8:21 [PATCH] MdePkg DxeServicesLib: Handle potential NULL FvHandle Star Zeng
2017-05-05 9:10 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14D72A993@shsmsx102.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